Open
Conversation
…ror has no limits configured
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
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.
Description
Add optional chaining to
this.config.limits?.eventinStaticMirroringWorker.canAcceptEvent()Related Issue
Fixes #567
Motivation and Context
Mirror.limitsis typed as optional but was accessed without optional chaining. When a mirror entry has nolimitsblock configured, this throws a TypeError inside the message handler which gets swallowed by the surrounding try/catch. So the mirror connects and subscribes fine, but silently drops every incoming event.How Has This Been Tested?
Manually configured a mirror entry without a
limitsblock and confirmed events are stored correctly after the fix.Screenshots (if appropriate):
N/A
Types of changes
Checklist: