Northeastern-Electric-Racing / Northeastern-Electric-Racing/Calypso
Dump current configuration after built
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 2
- Avg merge
- 6d 20h
- Merged PRs (30d)
- 3
Description
Description
Right now, new versions of Calypso are deployed onto the car via Odysseus very often. The actual configurations those versions contain is very uncertain.
Acceptance Criteria
- A way to see what CANGEN configuration was passed in when built, at runtime when deployed onto the car
Proposed Solution
Since space is not an issue, a way to embed the JSON files and re-print them via a command line flag would be very useful. perhaps a hash or something of the configuration that is reproducible, which could then be compared to a CI version or something. Perhaps a Git SHA or something.
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.
Research direction
Start by locating where CANGEN configuration JSON files enter the build and where Calypso defines its command-line flags. Trace how the built configuration reaches runtime on the car. Done means a runtime command-line option can show the configuration used at build time, with a reproducible identifier if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100