Skip to content

Correct error messages that do not name their code. - #6

Open
echennells wants to merge 1 commit into
masterfrom
fix-suspended-error-messages
Open

echennells wants to merge 1 commit into
masterfrom
fix-suspended-error-messages

Conversation

@echennells

@echennells echennells commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Three entries in the error message table do not name their code. suspended_channel carries the text of sacrificed_channel, so a channel stopped by store suspension renders identically to the continuous download work redistribution; suspended_service renders as "sacrificed service", and validate10 as "validate0", neither of which is a code.

The messages now name their codes. The unit tests asserted the copied text and are updated with them.

@echennells
echennells force-pushed the fix-suspended-error-messages branch from 1f1395d to 96f9378 Compare August 24, 2026 16:31
@echennells
echennells force-pushed the fix-suspended-error-messages branch 2 times, most recently from 464c3e0 to 98b09aa Compare September 18, 2026 15:50
suspended_channel carries the message text of sacrificed_channel, so a
channel stopped by store suspension renders identically to the routine
download work redistribution. suspended_service renders as "sacrificed
service" and validate10 as "validate0", neither of which is a code. The
unit tests asserted the copied text and are updated.
@echennells
echennells force-pushed the fix-suspended-error-messages branch from 98b09aa to 51bc86c Compare September 19, 2026 02:18
@echennells echennells changed the title Correct suspended_channel and suspended_service message text. Correct error messages that do not name their code. Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant