Andrey Larionov

I created a draft PR not only to declare my intention to fix this issue but also to provide a reproduction case to anyone who decided to make their own...

Oh, This is a tricky one. I spent quite some time locating the cause and still could not figure out the best approach to fix it. So let me explain...

@curquiza please, take a look at the previous comment. I believe this issue requires an additional round of triage.

Reordering of fields occurs in `milli/src/update/index_documents/transform.rs:545` `remap_index_documents`, which is called from `milli/src/update/settings.rs:269` `reindex`.

Here are the reproduction steps for the scenario I mentioned: ``` curl -X POST -H "Content-Type: application/json" --data-binary '{"uid": "field_order_test", "primaryKey": "id"}' http://localhost:7700/indexes curl -X POST -H "Content-Type: application/json" --data-binary...

@Kerollmops, so, if you have already decided to reimplement document storage with new requirements, then I do not see any reason for trying to fix this issue in the current...

Strange. Readme state ssh-agent support, but what it means if there is no agent forwarding?

Ok. I will close it then.

Looks like in these conditions, the webhook for this event is also not triggered.

Additional information is useful. Today, we upgraded the instance to the latest 1.49.1 version. Querying `/user/search` does not return `verifiedInstant` fields for user or registration. However, according to documentation, this...