eclipse-score / eclipse-score/orchestrator

Bug: Bound invokes to dedicated worker are not respected in graph action

Open
#58 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/380
-----

### Describe the bug:

Actions bound to dedicated worker are executed on different threads when they are included in Graph.

### 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.dedicated_graph --input '{"runtime": {"task_queue_size": 256, "workers": 4, "dedicated_workers": [{"id": "dedicated_worker_0"}]}}'`

### Observed behavior:
All sync funtions 1-5 are reported to be executed on different threads (workers).
### Expected behavior
As all tags are bound to the same dedicated worker they should be executed on the same thread.
You can compare that commented concurrency code in `graph_with_dedicated` in `component_integration_tests/rust_test_scenarios/src/tests/orchestration/orchestration_graph.rs` works correct - all actions are executed on the same thread.

### 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.