- LongPath.expected: revert wrong rebless from 69c27c53c1b. CI generates
the long-path file during build, so the long-path entry is correct.
- 4 framework/query DataFlowConsistency.expected: pure toString polish
(ControlFlowNode for X -> X / After X).
- essa/ssa-compute/CONSISTENCY/TypeTrackingConsistency.expected: deleted.
The 6 prior 'unreachable node in step of kind ...' violations are gone
under the new SSA; per CI auto-rebless convention the empty file is
removed.
- extractor-tests/syntax_error/CONSISTENCY/CfgConsistency.expected: new.
Documents one expected deadEnd on `break` outside any loop in the
syntax-error test corpus.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The shared CFG library overrides ControlFlowNode.toString() as 'final'
(shared/controlflow/codeql/controlflow/Cfg.qll:1217), so the legacy
'ControlFlowNode for X' prefix is gone — the new toString returns just
'X' for normal nodes and 'After X' for after-nodes. This produces a
large cosmetic diff in test expected files with no semantic change.
Mass-rebless 78 .expected files whose actual output differs from the
checked-in expected only by this rename. Each file was verified to be
identical after normalising 'ControlFlowNode for ' and 'After ' away
from both sides.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
As discussed in a meeting today, this will end up presenting an query
suite that's easier to use for customers.
Since https://github.com/github/codeql/pull/6589 has JUST been merged,
if we get this change in fast enough, no end-user will ever have run
`py/sqlalchemy-textclause-injection` as part of LGTM.com or Code
Scanning.
We were mixing between things, so this is just to keep things
consistent. Even though it's not strictly needed for all queries,
it does look nice I think
