-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-06-23
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Graphite has found the issue:
The assertion message references transitionRes0 but should reference transitionRes1 to match the variable being tested in this context. This creates an inconsistency with the surrounding code pattern where the assertion message variable matches the variable being tested.
Suggested change123: transitionRes1);