Clarify required error information in lmcontrol API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with the lmcontrol API and the discussion in pull request 478, especially the linked comment, to identify the recovery and StateManager error-information use cases. Done means deciding whether and how the interface should expose failed components, intermediate transitions, and the active RunTarget.
Written by the indexing model from the issue text.
Description
What
Currently, the lmcontrol API will only provide an enum value as error information indicating if a RunTarget change happed due to a RecoveryAction or a StateManager request.
It is not possible to identify which components have failed in case the transition is triggered by a RecoveryAction.
It is not possible identify intermediate transitions that lead to the final RunTarget.
Knowing in which active RunTarget the error occurred requires tracking of the active RunTarget by the user of the API.
We shall clarify the use cases that need to be supported and extend the interface with the required information.
See also discussion here:
https://github.com/eclipse-score/lifecycle/pull/478#issuecomment-5365753698
Acceptance Criteria (DoD)
- Decide if and how to extend the interface with this error information
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 ·