Conversation
…kdown 'API total_supply:' in the feeder-gap and PoR-coverage alerts is invalid Markdown V1, so Telegram rejected it and the message was resent as plain text (literal asterisks), as seen on the 2026-09-23 08:05 feeder alert. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #373.
The feeder-gap and PoR-coverage alerts contained
API total_supply:. A bare_is invalid Telegram Markdown V1, so Telegram rejected the 2026-09-23 08:05uniBTC supply feeder wrongalert. It was resent as plain text, which is why literal*showed up (log:Markdown parse error from Telegram; retrying as plain text for unibtc).API total supply:._outside the link. I confirmed the test fails with the old label.Testing:
uv run pytestpasses (1345), andruff checkis clean.🤖 Generated with Claude Code