Fix problem due to LDMB update > 2.0.0 - #209
Merged
Merged
Conversation
Signed-off-by: Luca Foppiano <luca@foppiano.org>
Signed-off-by: Luca Foppiano <luca@foppiano.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When GROBID loads multiple DeLFT models sharing the same embeddings (e.g., glove-840B), only the first model loads. All others fail with:
lmdb 2.0.0 (released 2026-03-17) added a breaking change: "Opening the same LMDB path twice in one process now raises lmdb.Error instead of silently proceeding to a likely segfault" (#230).
The bug was always latent in DeLFT -- each Embeddings instance opens its own LMDB handle with no sharing. It only surfaced because lmdb is unpinned and Docker builds now pull 2.0.0.