Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cdc flow: continue as new after state updates #2420

Merged
merged 2 commits into from
Jan 9, 2025
Merged

Conversation

serprex
Copy link
Contributor

@serprex serprex commented Jan 9, 2025

this prevents rewinding state to start of workflow from undoing changes to settings (such as table additions/removals)

@serprex
Copy link
Contributor Author

serprex commented Jan 9, 2025

ideally we'd move to fully immutable state, but that just isn't the golang way

@iskakaushik
Copy link
Contributor

is there a way to write a test for this?

@serprex
Copy link
Contributor Author

serprex commented Jan 9, 2025

is there a way to write a test for this?

Maybe by checking that RunID changes. Will look into

@serprex serprex force-pushed the more-continue-as-new branch from 640370f to 068c67b Compare January 9, 2025 20:15
@serprex serprex force-pushed the more-continue-as-new branch 2 times, most recently from 10b0142 to 7caf976 Compare January 9, 2025 20:43
@serprex serprex enabled auto-merge (squash) January 9, 2025 20:43
this prevents rewinding state to start of workflow from undoing changes to settings (such as table additions/removals)
@serprex serprex force-pushed the more-continue-as-new branch from 7caf976 to 530d07f Compare January 9, 2025 20:44
@serprex serprex merged commit 48930ad into main Jan 9, 2025
9 checks passed
@serprex serprex deleted the more-continue-as-new branch January 9, 2025 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants