commitlog: Fix open flags for read-only offset index #2468
Merged
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.
For some reason, we've been opening the read-only index file with
.read(true).append(true).This translates to
O_RDWR | O_APPENDon *nix, but something weird onWindows. A shared memory map requires
O_RDWR(or equivalent) on eitherplatform, though, meaning that we'd always fail to
mmapthe index onWindows.
Open with
.read(true).write(true)instead to fix.Expected complexity level and risk
1
The impact of this bug is also small, because the offset index is not crucial
for standalone use. Who says, though, that Windows will never become a viable
server platform for SpacetimeDB?
Testing
Extends the tests to open an index using all three variants and perform lookups.