REACTO UI indicators do not update sequentially with interview progress

Open
#76 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
frontend

Research direction

Start the local server at http://127.0.0.1:3000/ and reproduce the interview flow described in the issue. Trace how REACTO indicators receive conversation-stage updates versus the editor's Code-stage update; done means R, E, A, C, T, and O light up sequentially and in real time.

Written by the indexing model from the issue text.

Description

Describe the bug
During the mock interview, the visual UI indicators for the REACTO framework (Repeat, Example, Approach, Code, Test, Optimize) do not update synchronously with the actual conversation flow.

For instance, when I successfully complete the R, E, and A stages verbally and begin typing my solution, the "C" (Code) indicator lights up, but the previous stages (R, E, A) remain unlit/empty. They often suddenly light up or fill in all at once much later in the session, rather than step-by-step as I complete them.

Expected Behavior
The REACTO UI indicators should light up sequentially and in real-time as the AI interviewer acknowledges the completion of each respective phase (R -> E -> A -> C -> T -> O).

Actual Behavior
The UI indicators are delayed and update out of order. 'C' might light up while 'R', 'E', and 'A' are still visually unlit, making it confusing for the candidate to track their current stage in the framework.

Steps to Reproduce

  1. Start a coding interview with Jim.
  2. Verbally complete the Repeat, Example, and Approach stages.
  3. Observe the REACTO UI indicators (they often remain unlit).
  4. Start typing in the editor (entering the Code stage).
  5. Observe the 'C' indicator lighting up while the previous stages are still empty, and watch them abruptly update later.

Environment

  • OS: Windows 11
  • Browser: Chrome
  • Access Method: Web browser via local server (http://127.0.0.1:3000/)
  • Git revision: 2c9e15107fe8bb4b5ee79fb35b857ca6b72e6f7d
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sysprog21/codetrial

All issues in sysprog21/codetrial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.