Files
matrix/discord-bridge
jaredandClaude Opus 5.5 d8c2acc461
Lint / Shell (shellcheck) (push) Successful in 29s
Lint / JS (eslint) (push) Successful in 27s
Lint / No Hookshot webhook IDs in README (push) Successful in 12s
Lint / No secrets in webhook configs (push) Successful in 8s
Lint / Landing page is rendered (matrix (push) Successful in 5s
Lint / Python (ruff) (push) Successful in 6s
Lint / Secret scan (gitleaks) (push) Successful in 7s
Lint / Shell (shellcheck) (pull_request) Successful in 7s
Lint / JS (eslint) (pull_request) Successful in 17s
Lint / No Hookshot webhook IDs in README (pull_request) Successful in 9s
Lint / No secrets in webhook configs (pull_request) Successful in 19s
Lint / Python deps (pip-audit) (push) Successful in 1m18s
Lint / Landing page is rendered (matrix (pull_request) Successful in 11s
Lint / Python (ruff) (pull_request) Successful in 22s
Lint / Secret scan (gitleaks) (pull_request) Successful in 7s
Lint / Python deps (pip-audit) (pull_request) Successful in 34s
discord-bridge: check the gateway echo before retrying ambiguous webhook sends
On 2026-11-15 21:34 an image relay failed with "read: connection reset by
peer" after the request was sent. Patch 0001 deliberately doesn't retry
those (a webhook post has no dedupe), so the image was dropped.

Patch 0002: while a relay send is in flight the bridge watches the
Discord gateway for its own post (same webhook, text and attachment
count, created after the send started). On an ambiguous failure (reset,
EOF, timeout waiting for the reply, Discord 5xx) it waits up to 6 s for
that echo: if it shows up the send counts as delivered and is recorded
(no resend, no copy back into Matrix); otherwise it retries with the
0001 backoff, checking again before each resend.

build-patched.sh runs the new tests with -race.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA
2026-11-15 21:42:47 -05:00
..