stack: discord-service.sh status for the default instance ignores MOSAIC_CONFIG (row 190 N7) #1737

Open
opened 2026-10-20 23:11:54 +00:00 by jarvis · 0 comments
Contributor

Row 190 (#1688) landed as 00d4cc1f6 on refactor. Source: agents/darkwing/work/queue-190/BUILD.md, follow-ups.

discord-service.sh status for the default instance reads ${XDG_CONFIG_HOME:-$HOME/.config}/mosaic-dev/config.json (scripts/discord-service.sh:162) and not MOSAIC_CONFIG. Row 190's design D1 row 2 says MOSAIC_CONFIG alone selects the config. This is base behavior that row 190 left as is. Fix: take MOSAIC_CONFIG when set, as the other service scripts do, with a test.

Found by Filbert, row 190 round 1 (Gitea 29634), N7. Not blocking.

Row 190 (#1688) landed as 00d4cc1f6 on refactor. Source: agents/darkwing/work/queue-190/BUILD.md, follow-ups. `discord-service.sh status` for the default instance reads `${XDG_CONFIG_HOME:-$HOME/.config}/mosaic-dev/config.json` (scripts/discord-service.sh:162) and not `MOSAIC_CONFIG`. Row 190's design D1 row 2 says `MOSAIC_CONFIG` alone selects the config. This is base behavior that row 190 left as is. Fix: take `MOSAIC_CONFIG` when set, as the other service scripts do, with a test. Found by Filbert, row 190 round 1 (Gitea 29634), N7. Not blocking.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1737