-
Notifications
You must be signed in to change notification settings - Fork 82
Force vendoring of LMDB even if a system version is available #699
Conversation
- don't use lmdb master3 branch anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that. What do you think @irevoire?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep perfect, thanks @dureuill
bors merge
699: Force vendoring of LMDB even if a system version is available r=irevoire a=dureuill # Pull Request ## Related issue Related to meilisearch/meilisearch#3017: will fix once ported to milli and meilisearch. ## What does this PR do? - Force using vendored version of LMDB - **don't use lmdb master3 branch anymore**: this is a bit of a side effect of using a tag instead of branch for heed as a dependency, but it is wanted anyway for now as lmdb master3 was more of an experiment ## PR checklist Please check if your PR fulfills the following requirements: - [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? Thank you so much for contributing to Meilisearch! Co-authored-by: Louis Dureuil <louis@meilisearch.com>
Build failed: |
bors merge |
699: Force vendoring of LMDB even if a system version is available r=irevoire a=dureuill # Pull Request ## Related issue Related to meilisearch/meilisearch#3017: will fix once ported to milli and meilisearch. ## What does this PR do? - Force using vendored version of LMDB - **don't use lmdb master3 branch anymore**: this is a bit of a side effect of using a tag instead of branch for heed as a dependency, but it is wanted anyway for now as lmdb master3 was more of an experiment ## PR checklist Please check if your PR fulfills the following requirements: - [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? Thank you so much for contributing to Meilisearch! Co-authored-by: Louis Dureuil <louis@meilisearch.com>
Build failed: |
bors merge |
699: Force vendoring of LMDB even if a system version is available r=irevoire a=dureuill # Pull Request ## Related issue Related to meilisearch/meilisearch#3017: will fix once ported to milli and meilisearch. ## What does this PR do? - Force using vendored version of LMDB - **don't use lmdb master3 branch anymore**: this is a bit of a side effect of using a tag instead of branch for heed as a dependency, but it is wanted anyway for now as lmdb master3 was more of an experiment ## PR checklist Please check if your PR fulfills the following requirements: - [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)? - [x] Have you read the contributing guidelines? - [x] Have you made sure that the title is accurate and descriptive of the changes? Thank you so much for contributing to Meilisearch! Co-authored-by: Louis Dureuil <louis@meilisearch.com>
Build failed: |
The PR now modifies CI to run cargo check on the release rather than the debug artifacts. This is an attempt to reduce the necessary disk space and avoid "out of space" failures. The idea is to avoid duplicating artifacts between debug and release, and also release artifacts are generally leaner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this ok for you @Kerollmops?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is ok for me but @dureuill could you document that in a separate issue because we could probably do better here by probably deleting the target repo or increasing the disk size instead.
bors merge
Opened a new issue like requested: meilisearch/meilisearch#3358 |
Pull Request
Related issue
Related to meilisearch/meilisearch#3017: will fix once ported to milli and meilisearch.
What does this PR do?
cargo check
on the release rather than the debug artifacts. This is an attempt to reduce the necessary disk space and avoid "out of space" failures.PR checklist
Please check if your PR fulfills the following requirements:
Thank you so much for contributing to Meilisearch!