Fixing flatbuffer store calculation to include prefix size #67
Conversation
This file contains 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
…ing flatbuffer to disk
nsmithtt
approved these changes
Jul 1, 2024
sdjordjevicTT
deleted the
sdjordjevic/fixing_flatbuffer_store_size_calculation#43
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We encountered an issue when storing the FlatBuffer to disk and rereading it from the saved file. The problem arose because we didn’t include the size of the prefix. The GetPrefixedSize function returns the size of the FlatBuffer, excluding the prefix size. To resolve this, I am updating the code to use GetSizePrefixedBufferLength instead. This function includes both the size of the prefix and the size of the FlatBuffer, ensuring accurate storage and retrieval.
[size prefix][flatbuffer]
|---------length--------|
Solves #43