Paste any cryptic error or stack trace — get what it actually means, the 3 most likely causes ranked, and the fastest check for each.
Decode this error for me. Context: {LANGUAGE/FRAMEWORK + what I was doing when it happened + what
I changed recently, if anything}.
Structure your answer:
1. TRANSLATION: what this error message actually says, in one plain-English sentence. (Error
messages describe symptoms — name the symptom.)
2. WHERE TO LOOK: which line/frame in the trace is MINE vs. library noise — point at the frame
that matters.
3. LIKELY CAUSES, ranked by probability for MY context: for each — why it produces exactly this message, and a 30-second check to confirm or eliminate it (a print, a command, an inspection).
4. THE FIX for the confirmed cause — and if we can't confirm yet, the fix for cause #1 with a note on what result means "move to cause #2".
5. UNDERSTAND IT ONCE: the 2-sentence concept behind this error class, so I recognize it instantly next time.
Rule: never say "this usually means" without committing to a ranked list. Vague error help is no help.
ERROR + STACK TRACE: {PASTE}
RELEVANT CODE (if I have it): {PASTE}