eclipse-score / eclipse-score/orchestrator

Bug: Actions share the same ID

Open
#59 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
5
Forks
18
Avg merge
15h 58m
Merged PRs (30d)
1

Description

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:
1. Checkout `git switch piotrkorkus_complex_graphs`
2. `cd component_integration_tests/rust_test_scenarios`
3. `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:

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.