Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Coding-only loop ended the session and jumped to the report with ~16 min left, while tests were 2/4 and code was still being edited

Fermée
  • Quelque chose ne va pas ?
#83 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
cpp
Domaine
full-stack

Piste de recherche

No source file or test is named. Start by reproducing the coding-only loop with a 30-minute Medium interview, incomplete code, and failing tests, then trace the REACTO completion, timer, and transition to the final report. Done means the session does not end before the selected duration or an explicit user action, including when REACTO steps appear complete.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Description:

In a Medium interview running in coding-only loop mode (behavioral round skipped), the session ended on its own and jumped to the final report with ~16 minutes still on the clock. My code was still being edited and the last test run was only 2/4 passing, yet all REACTO steps were shown as complete and Jim wrapped up the session. I did not choose to end the interview.

What happened:

Started a Medium interview, 30 min, in coding-only loop mode.
Worked through the problem; the REACTO tracker showed all steps checked: Repeat, Example, Algorithm, Coding, Test, Optimizations.
Ran the tests: result was 2/4 passed (FAIL two profitable swings: expected 7, got 14). I was still editing the code (line 12 was mid-typing) to fix the failing cases.
With the timer at 16:37 remaining, Jim said:
"Thanks so much for your time today, it was great speaking with you. Your performance report will be ready in just a moment."

The session ended and jumped straight to the final report, even though the code was incomplete and tests were not passing.
Expected:
The session should continue until the chosen duration elapses (or I end it), especially while tests are failing and the code is still being edited. Marking all REACTO steps complete should not end the session while tests are at 2/4.

Actual:
With ~16 minutes left, tests at 2/4, and code still being edited, all REACTO steps were marked complete and the session ended and jumped to the final report.

Reproducibility:
Observed once on 2026-09-21. I ran another interview the next day and it did not happen again, so I could not reproduce it. Reporting it as a real observed incident rather than a reliably reproducible one.

Screenshot:

Taken one second before the session jumped to the report
Image

Environment:

Date/time: 2026-09-21, ~20:10 (UTC+8)
OS: Windows 11
Browser: Microsoft Edge 153.0.4234.48
Interview mode: coding-only loop (behavioral round skipped)
Interview: Medium, duration 30 min
Problem: Single Slot Reseller
Language: C++
Timer at cutoff: 16:37 remaining
Test results at cutoff: 2/4 passed (FAIL two profitable swings: expected 7, got 14)
Report: generated normally (no error)
Git revision: 7efebb0 (7efebb002b7c2a3e9fb856a0855582d32ca77d98)

Langage dominant
Rust
Étoiles
177
Forks
100
Merge moyen
1 j 10 h
PR mergées (30 j)
191

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de sysprog21/codetrial

Toutes les issues de sysprog21/codetrial

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.