[crash] d1 (347e42beb9670300)

[Monkopedia]

Automated crash report from a foss-flavor build (ACRA → relay /crash).

• App version: 1.0.9
• App version code: 10
• Android version: 17
• Device model: Pixel 10 Pro XL
• Device brand: google
• Package: com.rousecontext

vg.d1: Job was cancelled; job=r1{Cancelled}@​ae199b1

[monkopedia-coder]

The relay filed this crash five times in one second — dedup is not working

#728, #729, #730, #731, #732 all carry fingerprint 347e42beb9670300 and byte-identical bodies (sha256 prefix 2b4df913118aba20 on all five), created at 2026-09-07T05:00:37Z — the same second. #729–#732 are now closed as duplicates of this one.

relay/relay.example.toml states the endpoint "sanitizes/dedups them into GitHub issues labeled crash", so this is the dedup path not doing what the config documents. Recording it here rather than opening a separate issue, since the backlog is deliberately frozen.

Worth noting for whoever picks it up: the other two reports from the same batch, #733 (638a69e1c9636e88) and #734 (e2e26dd88e2e763a), each filed exactly once — so the handler is not simply filing every POST. Five identical reports arriving simultaneously is the case that defeats it, which points at a check-then-file race rather than a missing check.

Crash filing is currently down regardless: the token in /etc/rouse-relay/env returns 401 Bad credentials, and RELAY_GITHUB_CRASH_TOKEN now holds a PAT with no Issues permission. A token minted with Issues: write and a relay redeploy are needed before any of this files again.