Repository navigation
fix: unblock stable release checks - #1897
Merged
Merged
Conversation
Skip unsupported test fixtures, synchronize retry readiness, and keep release notes concise.
Use the approved summary consistently in the bundled release text.
Require concurrent input reading so worker saturation cannot block protocol handling. Cover exhausted workers and unavailable concurrency, and ratchet the test baseline.
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
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.
Fix Windows test linking by skipping POSIX-only fixtures at compile time. Synchronize retry-cancellation checks with JSON worker readiness, and require concurrent JSON input reading so worker saturation cannot block protocol dispatch. Keep release notes concise.
These changes unblock the stable release without relaxing retry or cancellation assertions.