fix beacon-ness in legacy sync #4428
Merged
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
MaxMustermann2
approved these changes
May 11, 2023
ONECasey
approved these changes
May 11, 2023
sophoah
approved these changes
May 11, 2023
GheisMohammadi
added a commit
that referenced
this pull request
May 17, 2023
* fix beacon-ness * use enum to identify beacon shard
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.
Issue
This PR fixes beacon-ness in legacy sync.
Previously,
isBeaconparameter was hardcoded asfalsewhen called. Now, it is dynamic, based on the configuration. The parameter is only used in the logs.