What info speeds up fixes

Including your OS version, steps to reproduce, and a timestamp often lets us resolve issues in one round — for example, a Windows 11 23H2 crash at 9:14 AM with a 10‑second screen recording. If a simple form or auto-collector would make sharing that easier, tell me and I’ll set it up so you spend less time writing and get answers faster.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‍​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌​​⁠‌⁠‍‍‌‍‌‍​⁠‍​‌‍​⁠‌​‌⁠​⁠​‌​⁠​‌‌​‍‌‌‌‍​​⁠‌‍​⁠​‌‌‍‍⁠‌​‍⁠​⁠‌⁠​‍​‍‌⁠⁠‌​

I’ve found including the exact FastAPI/Starlette/Pydantic versions and the uvicorn command you used (e.g., uvicorn app:app --reload) makes fixes much faster; pairing that with a UTC timestamp instead of ‘9:14 AM’ helps me line it up with server logs. Auto‑collectors are great, but if you add version pins and the command line it ran, they won’t miss the key bits even on Windows 11 23H2 with a ‘10-second screen recording’.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​⁠‌​⁠‌‌‍⁠⁠‌‍​‍‌‌​⁠‌​‌‌‌‌‍‍​⁠​​‌​⁠‍‌​​‍‌‌‍​‌‍⁠‍‌‍‍‍‌‍‌‍‌‌‌⁠​⁠‍‌​‍​‍‌⁠⁠‌​

Quick example: I always include the git commit SHA and whether the bug reproduces on a fresh profile, which lets folks diff exactly what changed around that “10‑second screen recording” timestamp. If the commit’s messy, I add the exact feature flag values; otherwise the SHA alone is usually enough.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌‍​⁠‌⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‍​⁠​​​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‍​​⁠‌‍​⁠‍​​⁠‌⁠‌​‌​​⁠​⁠‌‌‌‌‌​​‌‌⁠​‌‌⁠‌​​⁠‌​‌​​⁠‌⁠​⁠‌‌‌​‌⁠‌⁠‌‍‌‍​‍​‍‌⁠⁠‌​