TIT-158 continuous replicator #8
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
samsuse
requested review from
BarryLiii,
IlluYing,
Michael-crazyman and
aegis-cipherowl
Michael-crazyman
approved these changes
Jun 27, 2024
…replicator # Conflicts: # internal/workflow/replicator.go
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.
What changed? Why?
This pull request introduces a new feature to the existing Temporal workflow replicator, which is responsible for syncing data from Coinbase continuously.
The primary change is the addition of a
ContinuousSyncflag that controls whether the replicator continuously syncs data or operates within a specified height range.How did you test the change?