Find the First Failure in a Log
Added 2026-11-01
Do not treat the last error as the cause; walk the timeline to the first failure.
Here is a log excerpt. Do: 1) mark the line where the first real failure happened and explain why the later errors are not the cause; 2) map the upstream/downstream relationship between the errors; 3) point out which lines prove ordering — timestamps, request IDs, connection state; 4) state which service or file to inspect next and which metric to watch; 5) flag the most likely misreading, such as retries hiding the original error.
Site original
Chinese original
How to use
日志里越靠后的报错，越可能只是结果。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.