qwen-code race: GitHub bot silently drops comments at the poll-cursor boundary second
wenshao · ghdev · 2026-11-04
Issue #16227 on QwenLM/qwen-code documents a real, reproducible silent-loss path: if a user comment's createdat lands exactly on the whole second the bot's poll cursor has already committed to, and its thread notification arrives late, the comment is filtered out on every later re-list by the strict createdat > windowSince bound — permanently skipped, marked read, with no error, dead-letter, or retry. The user just sees the bot never respond.
Root cause: the cursor derives from notification updatedat at second precision but is compared strictly against comment timestamps. An audit probe confirmed the boundary-second comment is dropped while a +1s control comment dispatches normally — a textbook timestamp-precision pitfall in polling integrations.
More from coding & agent
- Dev proposes LLM-generated ultra-rare content to build anime-style MMORPGs — rickasaurus · 2026-11-04
- Dev builds Chrome extension to bring back the classic Twitter bird on X — joonasvirtanen · 2026-11-04
- Developer lets his app record 'wishes' and auto-spawn OpenCode background agents to fulfill them — SubtleGradient · 2026-11-04
- Post-train your model on your own agent harness with OpenHands, Harbor, SkyRL and Snowflake — StasBekman · 2026-11-04
- Google Antigravity redesign leaked with context usage and quota indicators — clmt · 2026-11-04
- Microsoft's 4B Mage-VL-Cowork Hits 66% on OSWorld-Verified, Near Human Level — microsoft · 2026-11-04