[Bug]: Config parse errors, with config.toml lines, are sent to every signed-in user
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start at the subscription handler in src/api/events.rs around line 132, where every subscriber receives the event, and follow how me and libraries are threaded into translate. Then read src/config/store.rs around line 356 to see exactly what Event::ConfigError carries. Done means a non-admin receives a plain ConfigChanged with no error text while an admin still sees it, with the admin flag passing cleanly through translate; check the existing events tests for the pattern.
Written by the indexing model from the issue text.
Description
[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a code review session with @PhrolovaMoe. It was found by reading the code and hasn't been reproduced on a running server.
Version
0.40.0 (feat/desktop, 017a837b)
Area
Config
What happened?
When config.toml changes on disk and fails to parse, the watcher sends Event::ConfigError with the parser's message (src/config/store.rs:356). The events subscription passes it to every subscriber, admin or not (src/api/events.rs:132). toml's error message quotes the offending line, so if that line holds a TMDB key, SMTP password or Torznab API key, every signed-in user receives it.
Steps to reproduce
- Sign in as a non-admin in one browser and keep a page open (it subscribes to events).
- Break a line containing a secret in
config.toml, e.g.api-key = "abc(missing quote). - The non-admin's
eventssubscription gets aConfigChangedwith the line inerror.
Expected behavior
Only admins get the error text; everyone else gets a plain ConfigChanged (or nothing).
Suggested fix
Filter Event::ConfigError (and ConfigChanged) by is_admin in translate, which needs the user's admin flag passed in alongside me and libraries.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- Avg merge
- 4h 49m
- Merged PRs (30d)
- 5
Getting set up
- Ships a 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 tinystream-dev/tinystream
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tinystream-dev/tinystream#132 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tinystream-dev/tinystream#131 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
tinystream-dev/tinystream#129 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tinystream-dev/tinystream#128 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tinystream-dev/tinystream#124 ·
All issues in tinystream-dev/tinystream
Similar issues
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug QA/dev-automation
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day