3258: Bump milli to v0.37.4 r=curquiza a=Kerollmops
This PR bumps the milli dependency to v0.37.4 for the next Meilisearch release.
Co-authored-by: Kerollmops <clement@meilisearch.com>
3254: Update version for the next release (v0.30.4) in Cargo.toml files r=curquiza a=meili-bot
⚠️ This PR is automatically generated. Check the new version is the expected one before merging.
Co-authored-by: curquiza <curquiza@users.noreply.github.com>
3248: Bump milli to v0.37.3 r=curquiza a=Kerollmops
This PR bumps the milli dependency from v0.37.2 to v0.37.3.
Co-authored-by: Kerollmops <clement@meilisearch.com>
3240: Update version for the next release (v0.30.3) in Cargo.toml files r=curquiza a=meili-bot
⚠️ This PR is automatically generated. Check the new version is the expected one before merging.
Co-authored-by: curquiza <curquiza@users.noreply.github.com>
3237: Fix the cli flags related to the import of dump and snapshot. r=dureuill a=irevoire
Some flags were badly applied + the database wrongly deleted when it shouldn't.
To reduce the number of mistakes we might make I added a bunch of comments + created a function that handles the import of an existing or empty database.
Here is the associated (working) code from the v0.29.3: https://github.com/meilisearch/meilisearch/blob/release-v0.29.3/meilisearch-lib/src/dump/mod.rs#L166-L191
Fix #3238
Co-authored-by: Tamo <tamo@meilisearch.com>
3218: Update version for the next release (v0.30.2) in Cargo.toml files r=curquiza a=meili-bot
⚠️ This PR is automatically generated. Check the new version is the expected one before merging.
Co-authored-by: curquiza <curquiza@users.noreply.github.com>
3217: Bump milli to v0.37.2 r=Kerollmops a=curquiza
⚠️ Please ensure milli has been updated in EVERY cargo.tom ⚠️
Co-authored-by: curquiza <clementine@meilisearch.com>
3213: Fix the instance-uid in the data.ms r=Kerollmops a=irevoire
We were writing the instance-uid as bytes instead of strings in the data.ms, and thus we were unable to parse it later. Also, it was less practical for our users to retrieve it and send it to us.
Fix#3214
Co-authored-by: Tamo <tamo@meilisearch.com>
We were writing the instance-uid as bytes instead of string in the data.ms and thus we were unable to parse it later.
Also it was less practical for our user to retrieve it and send it to us.
3202: Bump milli to v0.37.1 r=curquiza a=Kerollmops
This PR bumps milli to v0.37.1 and fixes#3167, #3178, #3165, and #3021.
3203: Update version for the next release (v0.30.1) in Cargo.toml files r=Kerollmops a=meili-bot
⚠️ This PR is automatically generated. Check the new version is the expected one before merging.
Co-authored-by: Kerollmops <clement@meilisearch.com>
Co-authored-by: curquiza <curquiza@users.noreply.github.com>
3160: Clamp databases max size to the page size r=irevoire a=Kerollmops
This PR fixes#3150 (again #2662). We fix it again, here, as we entirely rewrote the index scheduler and forgot about this little detail.
`@irevoire` Can I have your input on where we create the indexes in the tests? I want to use a non-page-size rounded value in the tests. This way, we can see this issue in the tests next time.
Co-authored-by: Kerollmops <clement@meilisearch.com>
3161: « Fix » dump tests r=curquiza a=irevoire
This PR doesn't re-enable the dump tests.
It's a cherry-pick of https://github.com/meilisearch/meilisearch/pull/3149 that should avoid a conflict when we merge on `main` later
Close #3153
Co-authored-by: Tamo <tamo@meilisearch.com>
3085: refactorize the whole test suite r=irevoire a=irevoire
1. Make a call to assert_internally_consistent automatically when snapshotting the scheduler. There is no point in snapshotting something broken and expecting the dumb humans to notice.
2. Replace every possible call to assert_internally_consistent with a snapshot of the scheduler. It uses the same amount of lines and ensures we never change something without noticing in any tests ever.
3. Name every snapshot: it's easier to debug when something goes wrong and easier to review in general.
4. Stop skipping breakpoints; it's too easy to miss something. Now you must explicitly show which path the scheduler is supposed to use.
5. Add a timeout on the channel.recv, it eases the process of writing tests; now, when something files, you get a failure instead of a deadlock.
Co-authored-by: Irevoire <tamo@meilisearch.com>
3122: Display the `dumpUid` as `null` until we create it r=irevoire a=Kerollmops
This PR fixes#3117 by displaying the `DumpCreation` `dumpUid` details field as `null` until we compute the dump and the task is finished.
Co-authored-by: Kerollmops <clement@meilisearch.com>
1. Make a call to assert_internally_consistent automatically when snapshoting the scheduler. There is no point in snapshoting something broken and expect the dumb humans to notice.
2. Replace every possible call to assert_internally_consistent by a snapshot of the scheduler. It takes as many lines and ensure we never change something without noticing in any tests ever.
3. Name every snapshots: it's easier to debug when something goes wrong and easier to review in general.
4. Stop skipping breakpoints, it's too easy to miss something. Now you must explicitely show which path is the scheduler supposed to use.
5. Add a timeout on the channel.recv, it eases the process of writing tests, now when something file you get a failure instead of a deadlock.
3110: Always display `deletedDocuments` in the `IndexDeletion` details r=ManyTheFish a=Kerollmops
This PR fixes#3108 by always displaying a `deletedDocuments` details info.
Co-authored-by: Kerollmops <clement@meilisearch.com>
3106: Fix linking error when building binaries for aarch64 r=curquiza a=Kerollmops
This PR tries to fix#3094. Please don't look too close. It will be horrifying 😱
You can look at [the status of the fix in the CI](https://github.com/meilisearch/meilisearch/actions/runs/3523723323/jobs/5908229083).
Co-authored-by: Kerollmops <clement@meilisearch.com>
3105: Fix publish release CI r=Kerollmops a=curquiza
Fix CI to avoid release creation when triggering manually the CI with `workflow_dispatch` -> only trigger the upload of binary when the event is `release` instead of different of `schedule`
Co-authored-by: curquiza <clementine@meilisearch.com>
3099: Add a dispatch to the publish binaries workflow r=curquiza a=Kerollmops
This PR adds a dispatch to the publish binaries workflow to help us debug #3094.
Co-authored-by: Kerollmops <clement@meilisearch.com>
