Conversation
Up till now AddEventDataStorageShmSizeAllocation was handed over an already calculated size for an internal EventDataStorage slot array. This mean, that the caller already anticipated, how EventDataStorage would internally store/layout its slots. This has been now fixed, by the caller just handing down the number of slots and the size of a slot element and the size calculation is left to AddEventDataStorageShmSizeAllocation, which is semantical the correct way.
crimson11
requested review from
LittleHuba,
bemerybmw,
castler,
hoe-jo and
limdor
as code owners
October 2, 2026 18:33
This branch has not been deployed
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.
Up till now AddEventDataStorageShmSizeAllocation was handed over an already calculated size for an internal EventDataStorage slot array. This mean, that the caller already anticipated, how EventDataStorage would internally store/layout its slots.
This has been now fixed, by the caller just handing down the number of slots and the size of a slot element and the size calculation is left to AddEventDataStorageShmSizeAllocation, which is semantical the correct way.