Shared CFG: check abrupt completion origins - #22423
Draft
yoff wants to merge 1 commit into
Draft
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
Adds shared CFG validation ensuring language-supplied abrupt completions originate from their associated in/additional node.
Changes:
- Registers invalidAbruptCompletionOrigin in CFG consistency checks.
- Adds generated regression coverage for Java, C#, and Python consumers.
| File | Description |
|---|---|
| shared/controlflow/codeql/controlflow/ControlFlowGraph.qll | Implements and registers the consistency check. |
| python/ql/test/library-tests/ControlFlow/successors/InvalidAbruptCompletionOrigin.ql | Adds Python validation. |
| python/ql/test/library-tests/ControlFlow/successors/InvalidAbruptCompletionOrigin.expected | Records expected Python results. |
| java/ql/test/library-tests/controlflow/basic/InvalidAbruptCompletionOrigin.ql | Adds Java validation. |
| java/ql/test/library-tests/controlflow/basic/InvalidAbruptCompletionOrigin.expected | Records expected Java results. |
| csharp/ql/test/library-tests/controlflow/graph/InvalidAbruptCompletionOrigin.ql | Adds C# validation. |
| csharp/ql/test/library-tests/controlflow/graph/InvalidAbruptCompletionOrigin.expected | Records expected C# results. |
Review details
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 7/7 changed files
- Comments generated: 0
- Review effort level: Balanced
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
All of the added qltests and corresponding expected files are unnecessary, since this is a consistency query. |
Sorry, something went wrong.
yoff
marked this pull request as draft
August 25, 2026 13:14
Copy link
Copy Markdown
Contributor
Author
|
Sorry, this was meant to be a draft. It is currently completely copilot, so I need to look it over. |
Sorry, something went wrong.
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.
Summary
This intentionally does not inspect the shared library's combined private beginAbruptCompletion, whose unmatched final catch-clause completion legitimately originates at isAfterValue.
Motivation
This follows the consistency-check suggestion from review of #22380: #22380 (comment). The change is independent of #22380 and contains no Python-specific CFG behavior change.
Validation
No invalid abrupt-completion origins or unrelated expected-output churn were found in the three consuming languages.