Bug 266027 - textproc/meilisearch
Summary: textproc/meilisearch
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Ashish SHUKLA
URL:
Keywords:
Depends on: 268916
Blocks:
  Show dependency tree / graph
 
Reported: 2022-08-25 06:19 UTC by andrew
Modified: 2023-02-26 12:39 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (ashish)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2022-08-25 06:19:24 UTC 

    


    


      



        
          Comment 1
        

        
          andrew

        

        
        

        
          2022-08-25 06:35:23 UTC
        

      






Port builds and runs successfuly. but when I start using this search engine by adding some json-data it brings: Invalid argument (os error 22)
debug logs of meilisearch has no error

step to reproduce
1. run meilisearch
2. curl -X POST 'http://localhost:7700/indexes/movies/documents'   -H 'Content-Type: application/json' --data-binary movies.json

ktrace dump 

1035 100141 meilisearch 0.046365 RET   munmap -1 errno 22 Invalid argument


https://wtools.io/paste-code/bEy4

    


    


      



        
          Comment 2
        

        
          andrew

        

        
        

        
          2022-08-26 20:00:50 UTC
        

      






maybe it helps:
update port version up to 0.22 and use sysinfo-0.25.0 crate

    


    


      



        
          Comment 3
        

        
          Ashish SHUKLA

        

        
            freebsd_committer
            freebsd_triage
        

        
          2022-08-30 08:23:30 UTC
        

      






Filed bug #266113 to fix the cause of munmap failure, but that still didn't fix this.

I'm testing their latest release candidate with sysinfo crate locally bumped to 0.25.3. I'll continue to investigate this.

    


    


      



        
          Comment 4
        

        
          Ashish SHUKLA

        

        
            freebsd_committer
            freebsd_triage
        

        
          2023-02-26 12:39:03 UTC
        

      






Hi,

An update has been committed in bug #268916. Could you please update, and test again ? If you're still getting failures then please re-open this PR, or file a new PR.

Until then, I'm marking this as resolved.

Thanks!