Fix repeated log event subscription bug#439
Merged
Merged
Conversation
The bug was caused by the alreadySubscribedToEvents flag not being set after a successful log event subscription. This meant that plc_tag_register_logger() could be called multiple times, causing an error.
Collaborator
|
Thanks! Not sure how that happened... |
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
2 participants
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.
Ran into this bug when a logging event was added to
LibPlcTag.LogEventmore than once. This led to an error fromplc_tag_register_loggerbeing called more than once. Seems like thealreadySubscribedToEventsflag wasn't being set true after the first subscription.