Skip to content

Initial attempt to fix carryover events issue on continue-as-new#496

Merged
sophiatev merged 3 commits into
mainfrom
cgillum/fix387
Nov 11, 2025
Merged

Initial attempt to fix carryover events issue on continue-as-new#496
sophiatev merged 3 commits into
mainfrom
cgillum/fix387

Conversation

@cgillum

@cgillum cgillum commented Nov 7, 2025

Copy link
Copy Markdown
Member

This is an in-progress attempt to fix #387. These changes are really old and have been stashed away on my dev box for many months. I've merged it with the latest from main and fixed the merge conflicts to the best of my ability.

The bug can be reproduced using the ContinueAsNewEventsArePreserved test in test/Grpc.IntegrationTests/OrchestrationPatterns.cs.

As far as I remember, I haven't been able to get the test to pass. I'm creating this draft PR as a reference for someone who can hopefully carry this work to the finish line.

@sophiatev
sophiatev marked this pull request as ready for review November 11, 2025 01:28
Comment thread src/Shared/Grpc/ProtoUtils.cs
@cgillum

cgillum commented Nov 11, 2025

Copy link
Copy Markdown
Member Author

@sophiatev your changes look good to me. We'll need another person to sign off on this since I'm the original creator of this PR.

@sophiatev
sophiatev merged commit c1e25a4 into main Nov 11, 2025
4 checks passed
@sophiatev
sophiatev deleted the cgillum/fix387 branch November 11, 2025 18:33
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.

External events may be lost when using ContinueAsNew

3 participants