Allow for multiple ReadyConditions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with the flatbuffers config schema and the process_info_node component, then trace handleProcessStillStarting where ready conditions are handled. Resolve how multiple conditions are represented and processed, and verify that configuration accepts an array of supported ready conditions and the component handles them correctly.
Written by the indexing model from the issue text.
Description
What
The config field should allow for a list of Ready Conditions to be set.
Config
Schema
- The flatbuffers config schema shall declare a
ReadyConditionUnion type of all the currently supported ready conditions. - Change the component properties to
ready_conditionsand make it an array ofReadyCondition
CPP
This part might need some discussion.
How shall the ready conditions be stored?
std::vector? std::priotiy_queue?
with a priority_queue we could add a static member for PRIORITY for each ready condition implementation, then the order in which the ready conditions are processed can be defined?
Should the component implementation have it hard coded the order?
Component Implementations (process_info_node)
handleProcessStillStarting would need some changes as there we handle the ready conditions
Acceptance Criteria (DoD)
- Config allows for multiple ready conditions to be set.
How
No response
- Dominant language
- C++
- Stars
- 6
- Forks
- 34
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 83
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-score/lifecycle
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
eclipse-score/lifecycle#407 ·
-
cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eclipse-score/lifecycle#375 ·
-
Feature Req Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
eclipse-score/lifecycle#664 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
eclipse-score/lifecycle#652 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
eclipse-score/lifecycle#649 · 1 comment ·
All issues in eclipse-score/lifecycle
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·