Final report does not generate after manually ending a completed interview
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- full-stack
Research direction
Start CodeTrial locally at http://127.0.0.1:3000/ and reproduce a Coding interview with Jim that runs for more than 10 minutes before manually ending it. Trace the connection-lost state and final-report loading path. Done means the connection remains stable, or failures produce a visible error, and a manually ended completed interview displays its final report.
Written by the indexing model from the issue text.
Description
Description
I encountered this issue in several consecutive Coding interviews.
In almost every affected interview, CodeTrial shows a connection-lost notification after about 10 minutes. After completing the interview and manually clicking End Interview, the final report keeps loading without producing a result.
Steps to Reproduce
- Start CodeTrial locally at
http://127.0.0.1:3000/. - Start a Coding interview with Jim.
- Continue the interview for more than about 10 minutes.
- Observe a connection-lost notification.
- Complete the remaining interview steps and click End Interview manually.
- Wait for the final report.
Expected Behavior
The connection should remain stable throughout the interview.
After manually ending a completed interview, CodeTrial should generate and display the final report. If report generation fails, an error message should be shown.
Actual Behavior
A connection-lost notification appears after approximately 10 minutes.
After manually ending the interview, the report loading indicator keeps spinning without showing a result or error message. In one affected session, the interview lasted about 13 minutes and I waited 20 minutes for the report.
My internet connection was working normally.
Environment
- OS: macOS 26.5.2 (Build 25F84)
- Architecture: arm64 (Apple Silicon)
- Browser: Chrome
- Access method:
http://127.0.0.1:3000/ - Git revision:
a728cdd
- Dominant language
- Rust
- Stars
- 54
- Forks
- 8
- Avg merge
- 11h 57m
- Merged PRs (30d)
- 44
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sysprog21/codetrial
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
All issues in sysprog21/codetrial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100