Describe the bug:
All actions of the same type Sequence / Concurrency / Graph share the same TAG ID when printing program representation.
Steps to reproduce the behavior:
- Checkout
git switch piotrkorkus_complex_graphs
cd component_integration_tests/rust_test_scenarios
cargo run -- --name orchestration.graphs.integration_graph --input '{"runtime": {"task_queue_size": 256, "workers": 4}, "test":{"design_name":"two_steps"}}'
Observed behavior:
Program - GraphDesignProgram
Body:
|-Sequence - Tag(id:10179971130519446671, str: orch::internal::sequence)
|step
|-LocalGraphAction - Tag(id:8572010998622897224, str: orch::internal::graph)
|node 0 { indegree: 0, edges: [1] }
|node 1 { indegree: 1, edges: [] }
|step
|-LocalGraphAction - Tag(id:8572010998622897224, str: orch::internal::graph)
|node 0 { indegree: 0, edges: [1] }
|node 1 { indegree: 1, edges: [] }
Both graphs share the same ID. The same would happen in case of two sequences or concurrencies in single program.
Expected behavior
Graphs and other actions should have unique ID allowing to distinguish which is which.
Occurrence:
Always
Attachments / Logs:
Original report: https://github.com/qorix-group/inc_orchestrator_internal/issues/381
Describe the bug:
All actions of the same type Sequence / Concurrency / Graph share the same TAG ID when printing program representation.
Steps to reproduce the behavior:
git switch piotrkorkus_complex_graphscd component_integration_tests/rust_test_scenarioscargo run -- --name orchestration.graphs.integration_graph --input '{"runtime": {"task_queue_size": 256, "workers": 4}, "test":{"design_name":"two_steps"}}'Observed behavior:
Both graphs share the same ID. The same would happen in case of two sequences or concurrencies in single program.
Expected behavior
Graphs and other actions should have unique ID allowing to distinguish which is which.
Occurrence:
Always
Attachments / Logs: