HackerTrans
TopNewTrendsCommentsPastAskShowJobs

moatmoat

no profile record

Submissions

From Any ePub to Audiobook

github.com
2 points·by moatmoat·vor 4 Monaten·0 comments

Unlocking full-body human motor learning at scale

amathislab.github.io
3 points·by moatmoat·vor 5 Monaten·0 comments

Testing Frontier Vision-Language Models on Mazes and Handwriting. They Failed

inkslop.github.io
1 points·by moatmoat·vor 6 Monaten·0 comments

Modern Lab Page Template

github.com
1 points·by moatmoat·vor 9 Monaten·0 comments

A postmortem of three recent issues

anthropic.com
381 points·by moatmoat·vor 10 Monaten·116 comments

comments

moatmoat
·vor 10 Monaten·discuss
TL;DR — Anthropic Postmortem of Three Recent Issues

In Aug–Sep 2025, Claude users saw degraded output quality due to infrastructure bugs, not intentional changes.

The Three Issues 1. *Context window routing error* - Short-context requests sometimes routed to long-context servers.

   - Started small, worsened after load-balancing changes.
2. *Output corruption* - TPU misconfigurations led to weird outputs (wrong language, syntax errors).

   - Runtime optimizations wrongly boosted improbable tokens.
3. *Approximate top-k miscompilation* - A compiler bug in TPU/XLA stack corrupted token probability selection.

   - Occasionally dropped the true top token.
Why It Was Hard to Detect - Bugs were subtle, intermittent, and platform-dependent.

- Benchmarks missed these degradations.

- Privacy/safety rules limited access to real user data for debugging.

Fixes and Next Steps - More sensitive, continuous evals on production.

- Better tools to debug user feedback safely.

- Stronger validation of routing, output correctness, and token-selection.