This repository was archived by the owner on Jun 2, 2026. It is now read-only.
fix(callbacks): Validate callbacks exists - #53
Merged
Conversation
ImDevinC
force-pushed
the
fix-callback-checks
branch
from
October 13, 2025 15:31
54dc175 to
e620654
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
With the new logic that validates the socket connection, there is a potential race condition where
the callback isn't registered, which leads to a python error (
nonetype is not iterable). Thismakes sure that the key exists before trying to call it, thus preventing that error.
Fixes #52