[bug] akkoma returns ArgumentError on newest meilisearch #578

Closed
opened 2023-07-03 21:13:26 +00:00 by Ghost · 3 comments

Your setup

Docker

Extra details

No response

Version

8c956bc671

PostgreSQL version

No response

What were you trying to do?

I updated meilisearch to 1.2.0 and I think they introduced some breaking changes. Search no longer works at all and instead returns an argument error in akkoma's logs.

What did you expect to happen?

Being able to search and see search results.

What actually happened?

ArgumentError instead

Logs

```
21:07:41.740 [error] Task #PID<0.3826.0> started from #PID<0.3822.0> terminating
** (ArgumentError) argument error
    (finch 0.14.0) lib/finch/http1/pool.ex:72: Finch.HTTP1.Pool.request/5
    (finch 0.14.0) lib/finch.ex:324: anonymous fn/4 in Finch.request/3
    (telemetry 0.4.3) /opt/akkoma/deps/telemetry/src/telemetry.erl:272: :telemetry.span/3
    (tesla 1.4.4) lib/tesla/adapter/finch.ex:63: Tesla.Adapter.Finch.call/2
    (tesla 1.4.4) lib/tesla/middleware/telemetry.ex:97: Tesla.Middleware.Telemetry.call/3
    (tesla 1.4.4) lib/tesla/middleware/follow_redirects.ex:46: Tesla.Middleware.FollowRedirects.redirect/3
    (pleroma 3.9.3-20-g8c956bc6-develop) lib/pleroma/search/meilisearch.ex:37: Pleroma.Search.Meilisearch.meili_post/2
    (pleroma 3.9.3-20-g8c956bc6-develop) lib/pleroma/search/meilisearch.ex:84: Pleroma.Search.Meilisearch.search/3
Function: &:erlang.apply/2
    Args: [#Function<1.36253945/1 in Pleroma.Web.MastodonAPI.SearchController.do_search/3>, [{"statuses", #Function<11.36253945/0 in Pleroma.Web.MastodonAPI.SearchController.do_search/3>}]]
```

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup Docker ### Extra details _No response_ ### Version 8c956bc671 ### PostgreSQL version _No response_ ### What were you trying to do? I updated meilisearch to 1.2.0 and I think they introduced some breaking changes. Search no longer works at all and instead returns an argument error in akkoma's logs. ### What did you expect to happen? Being able to search and see search results. ### What actually happened? ArgumentError instead ### Logs ````shell ``` 21:07:41.740 [error] Task #PID<0.3826.0> started from #PID<0.3822.0> terminating ** (ArgumentError) argument error (finch 0.14.0) lib/finch/http1/pool.ex:72: Finch.HTTP1.Pool.request/5 (finch 0.14.0) lib/finch.ex:324: anonymous fn/4 in Finch.request/3 (telemetry 0.4.3) /opt/akkoma/deps/telemetry/src/telemetry.erl:272: :telemetry.span/3 (tesla 1.4.4) lib/tesla/adapter/finch.ex:63: Tesla.Adapter.Finch.call/2 (tesla 1.4.4) lib/tesla/middleware/telemetry.ex:97: Tesla.Middleware.Telemetry.call/3 (tesla 1.4.4) lib/tesla/middleware/follow_redirects.ex:46: Tesla.Middleware.FollowRedirects.redirect/3 (pleroma 3.9.3-20-g8c956bc6-develop) lib/pleroma/search/meilisearch.ex:37: Pleroma.Search.Meilisearch.meili_post/2 (pleroma 3.9.3-20-g8c956bc6-develop) lib/pleroma/search/meilisearch.ex:84: Pleroma.Search.Meilisearch.search/3 Function: &:erlang.apply/2 Args: [#Function<1.36253945/1 in Pleroma.Web.MastodonAPI.SearchController.do_search/3>, [{"statuses", #Function<11.36253945/0 in Pleroma.Web.MastodonAPI.SearchController.do_search/3>}]] ``` ```` ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.
Ghost added the
bug
label 2023-07-03 21:13:26 +00:00

i can replicate this and i have NO idea why

finch just decides it doesn't want to connect

i'm investigating why it might do that

i can replicate this and i have NO idea why finch just decides it doesn't want to connect i'm investigating why it might do that

update i have found it, i think

#573

this pull here

works on 99.9999999% of cases
but because meili is local, and http and not https, i think mint goes haywire when given cacerts

let me try and work around it

update i have found it, i think https://akkoma.dev/AkkomaGang/akkoma/pulls/573 this pull here works on 99.9999999% of cases but because meili is local, and http and not https, i think mint goes haywire when given cacerts let me try and work around it

fixed via 31d7cc9a9c

fixed via 31d7cc9a9c4232a3184763e898330c8b2c5cc63d
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#578
No description provided.