fix: prevent checkpoint corruption and replay errors - #17
Merged
Merged
Conversation
…me to prevent checkpoint corruption and replay errors
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
2 participants
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.
Summary
JsonStringEnumConverterto checkpoint JSON serialization optionsFileCheckpointStore, preventing partial/corrupt checkpoints and replay errors on crash/power-lossThis commit was stranded on a parallel session's local
main(not pushed, branch push-protected). Rehomed onto its own branch per current CI-supply-chain-hardening guidance: no direct pushes tomain, every change goes through a PR.Test plan
dotnet buildsucceeds