fix: preserve incremental pipeline cancellation/cache stability - #117
Conversation
|
@coderabbitai autofix |
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThe PR introduces a new shared contract project ( 🚥 Pre-merge checks | ✅ 8 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (8 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 091d8f5f06
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| catch (OperationCanceledException) | ||
| { | ||
| // Cancellation must propagate so Roslyn can abort the pipeline. | ||
| throw; | ||
| } |
There was a problem hiding this comment.
Only rethrow cancellation tied to Roslyn token
This helper now rethrows every OperationCanceledException, which means selectors that throw OCE for reasons unrelated to the pipeline token (for example, a nested API using its own cancellation token) will abort generation and skip the SRE001 diagnostic path. That breaks the method’s “report exceptions and continue” behavior for a real class of failures; it should only propagate when the Roslyn cancellationToken is actually canceled (e.g., catch filter on cancellationToken.IsCancellationRequested or matching token).
Useful? React with 👍 / 👎.
Summary
Verification
Summary by CodeRabbit
New Features
Tests