UI not updating and timer keeps running after agent ends interview
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
Research direction
Reproduce the interview flow in the web app using the Coding + behavioral option and observe the closing message, timer, and chat state. Trace the interview-completion handling and timer logic from the relevant frontend entry points; done means the timer stops and the UI shows a clear report-generation or completed state.
Written by the indexing model from the issue text.
Description
Description
The AI agent concluded the interview, but the UI state did not update accordingly.
After the agent sent the concluding message below, the countdown timer kept running for nearly 40 seconds, and the UI showed no visual indicator that the interview had ended.
Jim: Thanks so much for your time today, it was great talking with you. Your written performance report is being prepared and will appear on your screen in a moment.
Steps to Reproduce
- Open the web app.
- Select Coding + behavioral
- Proceed through the interview until the agent sends the closing message.
- Observe the timer and the chat UI.
Expected Behavior
- Expected the timer to pause/stop once the agent indicates the interview is over.
- Expected some visual confirmation or transition state (e.g., "Generating report...") instead of the timer continuing to count down.
Actual Behavior
- The timer continues running (kept going for ~40 seconds).
- The UI remains unchanged with no indication that the session has ended.
Environment
- OS: macOS
- Browser: Brave
- Git revision d591c18
- Dominant language
- Rust
- Stars
- 94
- Forks
- 27
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 83
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 3/5 1-2 days Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
sysprog21/codetrial#222 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
sysprog21/codetrial#221 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
sysprog21/codetrial#220 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in sysprog21/codetrial
Similar issues
-
contribution
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tree-sitter/tree-sitter#6005 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
maplibre/maplibre-tile-spec#1844 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rust-windowing/winit#4731 ·
Maintainers usually reply within 2 days