Jim repeat the question for 2 times in the Robot Strides Plans solution and didnt end the conversation automatically
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- full-stack
Research direction
Start by reproducing the interview at http://127.0.0.1:3000/ with Jim, following the listed coding-interview steps. Trace the flow after the implementation, test cases, complexity, and edge-case discussion; done means the problem is stated once, the report is delivered, and the interview closes automatically.
Written by the indexing model from the issue text.
Description
Description
During a coding interview, Jim states the problem twice. After the implementation passes all test cases and the complexity and edge-case discussion is done, Jim says he will send the report, but the session doesn't end.
Steps to Reproduce
- Open the app at http://127.0.0.1:3000/.
- Start a Coding interview with Jim.
- Wait for Jim to present the problem, then submit a working implementation.
- Complete the complexity and edge-case discussion.
Expected Behavior
- Jim states the problem once.
- After all test cases pass and the complexity and edge-case analysis is complete, Jim delivers the report and the interview ends automatically.
Actual Behavior
- Jim repeats the problem statement a second time.
- After saying he'll send the report, the conversation stays open and the interview doesn't end.
Environment
OS: Mac OS 26.4
Browser: Chrome
Access Method: Web browser via local server (http://127.0.0.1:3000/)
Interview type: Coding interview
Github Version
a388302
- 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 4/5 3-5 days Newbie friendliness 55/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