Report command availability and reject unavailable commands
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Read the design and open questions in contracts issue #6, then the availability definition in contracts issue #13. Trace how firmware derives vehicle state and handles incoming commands; the payload does not name specific files or tests. Done when availability is reported as defined and unavailable commands are rejected with the new status code, including when the app sends them anyway.
Written by the indexing model from the issue text.
Description
Part of https://github.com/OpenCarControls/contracts/issues/6, which has the design and open questions.
Work out availability from the vehicle state, send it as defined in https://github.com/OpenCarControls/contracts/issues/13, and reject unavailable commands with the new status code even if the app sends them anyway.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 OpenCarControls/firmware
-
Refresh stale docsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
OpenCarControls/firmware#35 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
OpenCarControls/firmware#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenCarControls/firmware#31 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
OpenCarControls/firmware#30 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenCarControls/firmware#57 ·
Maintainers usually reply within 1 day
All issues in OpenCarControls/firmware
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
pedrovgs/UseCaseCoverage#23 ·
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
storytold/photocraft#8687 · 1 comment ·
Maintainers usually reply within 2 days
-
area:kernel bug kernel-paused needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bherbruck/solvecraft#5055 · 2 comments ·
-
bug cli p3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day