-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Python: Add consistency check for PhaseDependentFlow
#15775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Python: Add consistency check for
PhaseDependentFlow
This would have found the problem in #15755. As highlighted in the comment in the code, it's not a perfect solution since we don't have an automatic way to ensure we don't introduce a new PhaseDependentFlow use with a new step relation and forget to add it to this consistency check... but I think this consistency check still adds value!
- Loading branch information
commit d182eae868aada28abe51ba5a29da13210f0fa16
There are no files selected for viewing
21 changes: 21 additions & 0 deletions
21
python/ql/consistency-queries/PhaseDependentFlowConsistency.ql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| private import python | ||
| private import semmle.python.dataflow.new.DataFlow::DataFlow | ||
| private import semmle.python.dataflow.new.internal.DataFlowPrivate as DataFlowPrivate | ||
| private import semmle.python.dataflow.new.internal.VariableCapture as VariableCapture | ||
|
|
||
| from Node node | ||
| where | ||
| not exists(node.getScope()) and | ||
| exists(Node nodeFrom, Node nodeTo | node in [nodeFrom, nodeTo] | | ||
| // the list of step relations used with PhaseDependentFlow has been compiled | ||
| // manually, and there isn't really a good way to do so manually :| | ||
| DataFlowPrivate::LocalFlow::definitionFlowStep(nodeFrom, nodeTo) | ||
| or | ||
| DataFlowPrivate::LocalFlow::expressionFlowStep(nodeFrom, nodeTo) | ||
| or | ||
| DataFlowPrivate::LocalFlow::useUseFlowStep(nodeFrom, nodeTo) | ||
| or | ||
| VariableCapture::valueStep(nodeFrom, nodeTo) | ||
| ) | ||
| select node, | ||
| "Node being used in PhaseDependentFlow does not have result for .getScope(), so will not work properly (since division into run-time/import-time is based on .getScope result)" | ||
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.
Uh oh!
There was an error while loading. Please reload this page.