Meilisearch errors on finding object without publish date #326

Closed
opened 2022-12-01 12:48:33 +00:00 by Ghost · 3 comments

My instance is currently on develop commit 0cfd5b4e89.

When I try to index meilisearch, I am given an error:

$ MIX_ENV=prod mix pleroma.search.meilisearch index
Created indices. Starting to insert posts.
Entries to index: 662147
** (FunctionClauseError) no function clause matching in Calendar.ISO.parse_utc_datetime/2    
    
    The following arguments were given to Calendar.ISO.parse_utc_datetime/2:
    
        # 1
        nil
    
        # 2
        :extended
    
    Attempted function clauses (showing 1 out of 1):
    
        def parse_utc_datetime(string, format) when is_binary(string) and format === :basic or format === :extended
    
    (elixir 1.14.0) Calendar.ISO.parse_utc_datetime/2
    (elixir 1.14.0) lib/calendar/datetime.ex:1169: DateTime.from_iso8601/3
    (pleroma 3.4.0-135-ga8f3cf65-develop) lib/pleroma/search/meilisearch.ex:132: Pleroma.Search.Meilisearch.object_to_search_data/1
    (elixir 1.14.0) lib/stream.ex:612: anonymous fn/4 in Stream.map/2
    (elixir 1.14.0) lib/enum.ex:4751: Enumerable.List.reduce/3
    (elixir 1.14.0) lib/stream.ex:1026: Stream.do_transform_inner_list/7
    (elixir 1.14.0) lib/stream.ex:1811: Enumerable.Stream.do_each/4
    (elixir 1.14.0) lib/stream.ex:942: Stream.do_transform/5

My instance is currently on `develop` commit `0cfd5b4e89`. When I try to index meilisearch, I am given an error: ``` $ MIX_ENV=prod mix pleroma.search.meilisearch index Created indices. Starting to insert posts. Entries to index: 662147 ** (FunctionClauseError) no function clause matching in Calendar.ISO.parse_utc_datetime/2 The following arguments were given to Calendar.ISO.parse_utc_datetime/2: # 1 nil # 2 :extended Attempted function clauses (showing 1 out of 1): def parse_utc_datetime(string, format) when is_binary(string) and format === :basic or format === :extended (elixir 1.14.0) Calendar.ISO.parse_utc_datetime/2 (elixir 1.14.0) lib/calendar/datetime.ex:1169: DateTime.from_iso8601/3 (pleroma 3.4.0-135-ga8f3cf65-develop) lib/pleroma/search/meilisearch.ex:132: Pleroma.Search.Meilisearch.object_to_search_data/1 (elixir 1.14.0) lib/stream.ex:612: anonymous fn/4 in Stream.map/2 (elixir 1.14.0) lib/enum.ex:4751: Enumerable.List.reduce/3 (elixir 1.14.0) lib/stream.ex:1026: Stream.do_transform_inner_list/7 (elixir 1.14.0) lib/stream.ex:1811: Enumerable.Stream.do_each/4 (elixir 1.14.0) lib/stream.ex:942: Stream.do_transform/5 ```

it's not that it "no longer works", it's that you've somehow managed to get an object without a publish time

no idea how that would even happen

it's not that it "no longer works", it's that you've somehow managed to get an object without a publish time no idea how that would even happen
Ghost changed title from Meilisearch no longer seems to work to Meilisearch errors on finding object without publish date 2022-12-02 15:15:52 +00:00
Author

I have no idea either. My first thought that perhaps it had to do with the malicious servers that have been popping up, but I am not certain that's a cause. My elixir and postgres query skills are seemingly insufficient for finding the problem but I'll keep looking.

I have no idea either. My first thought that perhaps it had to do with the malicious servers that have been popping up, but I am not certain that's a cause. My elixir and postgres query skills are seemingly insufficient for finding the problem but I'll keep looking.
Author

I fixed it by setting config :pleroma, :instance, remote_post_retention_days to 1, then running database prune, and setting it back to 90.

I fixed it by setting `config :pleroma, :instance, remote_post_retention_days` to 1, then running database prune, and setting it back to 90.
Ghost closed this issue 2022-12-02 19:20:53 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#326
No description provided.