warrenwyf

> Do you build OSRM manually? We probably should have disabled asserts in Release mode 🤔 No, I used the prebuilt binary from node-osrm: https://github.com/Project-OSRM/osrm-backend/releases/download/v5.26.0/node_osrm-v5.26.0-node-v93-darwin-x64-Release.tar.gz

> Actually, I'm also getting assertions on the Linux release build too. Now I am confused. Yes, but the executable files in the docker image seems to be fine

> We have not seen this error before, is your query very complex? No, just create an empty table and try to create index on the vector field. btw, this...

Update: Get this error again: PANIC: ERRORDATA_STACK_SIZE exceeded, it seems that setting max_stack_depth does not fundamentally solve the problem.

Did not do any special operation, suddenly abnormal, the service is started through docker. The detail log: ``` [2024-04-18T08:01:19Z INFO service::utils::clean] Find directory "pg_vectors/indexes/101071". [2024-04-18T08:01:19Z INFO service::utils::clean] Find directory "pg_vectors/indexes/101076"....

The container has been running for several days, but restart does not make it work, I have already tried. There are only about 10 tables in the database, hundreds rows...

I notice the this line in the error log: ``` [2024-04-18T08:01:19Z ERROR vectors::bgworker] Panickied. Info: PanicInfo { payload: Any { .. }, message: Some(called `Result::unwrap()` on an `Err` value: Os...

Delete all index under `pg_vectors/indexes` and restart the container and `reindex database` seems solve the problem. However, I'm not sure if it won't be a problem without using scalar quantization....

There have been no error so far.

It should be possible to use the `docker buildx` command to cross-compile in the container and then copy the resulting files, but I don't know if this is possible in...