Restructure and clean node configuration pipeline
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading ark/client/comm_infrastructure/endpoint.py lines 37-121 to understand the current node configuration pipeline and its supported options. Clarify whether the intended result is path-based configuration, one configuration or CLI per node, global communication parameters, or serviceable parameters; done requires a decided design and corresponding simplified pipeline.
Written by the indexing model from the issue text.
Description
Current node configuration pipeline is convoluted, and a better solution is required.
- Too much freedom is given to the user (ie better to just get them always to simply pass a path).
- We can simplify to one configuration (or even simply a CLI) per node.
- Having a global configuration potentially still could be possible, eg for communication handling - ie parameters that apply to everything.
- Potential idea: make parameters automatically be serviceable (ie other nodes can retrieve parameter values)
- Dominant language
- Python
- Stars
- 623
- Forks
- 156
- PR merge metrics
- No merged PRs in 30d
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 Robotics-Ark/ark_framework
-
enhancement good first issue
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
Robotics-Ark/ark_framework#92 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Robotics-Ark/ark_framework
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100