serve: a start screen for people
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
Research direction
Read AGENTS.md, then inspect bloomery-serve output handling and crates/levers/src/registry.rs to find the record source and terminal settings. Design and implement a TTY-only screen that uses existing records, honors NO_COLOR and ASCII fallback, and can be disabled by a lever. Done when piped output stays unchanged and a golden test renders the screen from fixed records.
Written by the indexing model from the issue text.
Description
Today
At start, bloomery-serve prints key=value record lines: plan, load, host_tier, parallel, cache, residency, nvtier, and more. Tools read them, and they hold every fact. A person who just ran the command still has to read 20–40 dense lines to learn what happened: did the model fit, where did it go, and where do I send a request.
Wanted
A start screen for people that is fun to look at and informative. ASCII art is welcome. What it shows and how it looks is yours to design.
Rules (from AGENTS.md)
- The record lines stay as they are. The screen is a view over the same records, never a second source of a number. A value the load did not produce is not printed as if it were known.
- Only on a terminal. Draw it only when stderr is a TTY. Piped output is unchanged, because tests and toktape parse it.
- A way to turn it off: a lever row in
crates/levers/src/registry.rs. - Plain terminals still work: honour
NO_COLOR, and fall back to plain ASCII where the terminal has no UTF-8. - No load-time cost beyond formatting.
- A test: render the screen from a fixed set of records, and compare it with a golden text.
Screenshots from your terminal are welcome in the PR.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 4
- Avg merge
- 2h 32m
- Merged PRs (30d)
- 530
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 midagedev/bloomery
-
review-bot
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
review-bot
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
model
Difficulty 5/5 Over a week Newbie friendliness 25/100
midagedev/bloomery#698 · 3 comments ·
Maintainers usually reply within 1 day
-
model
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
model
Difficulty 5/5 Over a week Newbie friendliness 25/100
midagedev/bloomery#632 · 9 comments ·
Maintainers usually reply within 1 day
All issues in midagedev/bloomery
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rust-embedded/heapless#694 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
farion1231/cc-switch#8899 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
manuscript-lang/manuscript#1364 ·
Maintainers usually reply within 1 day