Dataflow: Add support for not skipping configuration-specific nodes in big-step#13717
Conversation
|
For a flow config using the new API (ConfigSig and so on) that does what I was expecting. I was a bit surprised that it didn’t do anything for old-style configuration classes. I guess it’s not important, as everything will move over to the new API in time. |
|
The C/C++ XXE query gets a bunch of additional steps due to its Is that desirable? Or should we add a Edit: There are also a bunch of other queries with additional steps where we might also want to consider whether or not to use the new default that this PR introduces. |
We resolved this on Slack and decided to add a |
owen-mc
left a comment
There was a problem hiding this comment.
Go 👍🏻 (but I think you should add a change note to let users know about the new feature)
f79b560
f79b560 to
8d365b0
Compare
|
One C/C++ query changed on main, so I had to rebase and add a commit to update its |
|
🚀 |
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration. Removed nodes and edges were only there originally due to multiple configurations being in scope. `DataFlow::PathNode` has union semantics for configurations. Nodes are only generated if they are reachable from a source, but this includes sources from other configurations.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration. Removed nodes and edges were only there originally due to multiple configurations being in scope. `DataFlow::PathNode` has union semantics for configurations. Nodes are only generated if they are reachable from a source, but this includes sources from other configurations.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
The extra nodes in .expected files are due to the changes from github#13717, which are not applied to configuration classes extending DataFlow::Configuration or TaintTracking::Configuration.
fixes https://github.com/github/codeql-team/issues/2191