-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FilterX: fix invalid LogMessage variables access #333
Merged
MrAnno
merged 7 commits into
axoflow:main
from
OverOrion:filterx-context-scope-fix-minimal
Oct 29, 2024
Merged
FilterX: fix invalid LogMessage variables access #333
MrAnno
merged 7 commits into
axoflow:main
from
OverOrion:filterx-context-scope-fix-minimal
Oct 29, 2024
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
OverOrion
force-pushed
the
filterx-context-scope-fix-minimal
branch
11 times, most recently
from
October 17, 2024 11:25
e67d698
to
88b4238
Compare
OverOrion
changed the title
filterx context scope fix minimal
FilterX: fix invalid LogMessage variables access
Oct 17, 2024
MrAnno
reviewed
Oct 22, 2024
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.
Nice 👍🏻
Signed-off-by: Szilard Parrag <[email protected]>
Signed-off-by: Szilard Parrag <[email protected]>
This is to better indicate the intention of synchronizing FilterX -> LogMessage. Signed-off-by: Szilard Parrag <[email protected]>
…rection Signed-off-by: Szilard Parrag <[email protected]>
Signed-off-by: Szilard Parrag <[email protected]>
Signed-off-by: Szilard Parrag <[email protected]>
A non-floating (i.e., tied to a LogMessage) FilterX variable is considered invalid if: - its' generation counter is 0 AND - the scope is syncable This is to allow two consecutive FilterX blocks to pass non-floating variables without calling filterx_scope_sync(). If they would be considered invalid then the changes would be lost in the latter block. This is because it would fetch it via _pull_variable_from_message() which would yield the unmodified LogMessageValue. Signed-off-by: Szilard Parrag <[email protected]>
OverOrion
force-pushed
the
filterx-context-scope-fix-minimal
branch
from
October 28, 2024 15:43
88b4238
to
afd3f19
Compare
MrAnno
approved these changes
Oct 29, 2024
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.
Nice :)
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.
This PR fixes accessing
LogMessage
type FilterX variables in case there had been changes betweenfilterx
blocks.