Maestro can only be initialized once #227
Merged
Conversation
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
Added logging for Maestro initialization status and handled cases for reinitializing it more than once.
tweska
approved these changes
Dec 16, 2025
Member
There was a problem hiding this comment.
If you can confirm my understanding is correct, then this looks fine to me.
Thank you for the fix!
Edit: Already confirmed in #200 (comment)
dsarmany
approved these changes
Dec 17, 2025
Contributor
Author
dsarmany
approved these changes
Jan 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Added logging for Maestro initialization status and handled cases for reinitializing it more than once.
Description
Maestro can only be intialized once from the same process. Upon trying to initializing maestro more than once, maestro returns status "MSTRO_NOT_TWICE". MaestroSink component should be able to handle this status correctly and continue working normally as this indicates maestro is already initialized and ready to work.
Fixes issue #200