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
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- full-stack
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
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)
- Lenguaje dominante
- Rust
- Estrellas
- 160
- Forks
- 64
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 114
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de sysprog21/codetrial
-
Highlight the active line in the code editorPosiblemente ocupada @ArthurArthurArthur0817 la tomó hace 8 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
sysprog21/codetrial#247 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Include local time in downloaded report filenamesPosiblemente ocupada @106081011 la tomó hoy. Abierto
sysprog21/codetrial#309 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Avoid automatic bracket pairing inside comments and stringsPosiblemente ocupada @Jonathas2127 la tomó hoy. Abierto
sysprog21/codetrial#307 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
Los mantenedores suelen responder en 1 día
-
Preserve test run historyPosiblemente ocupada @yunhsuan0510 la tomó hace 1 día. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 62/100
sysprog21/codetrial#301 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de sysprog21/codetrial
Issues similares
-
RUSTSEC-2026-0348: Brotli certificate decompression can allocate up to 1 GiB before authenticationAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 62/100
-
core: Amount::from_str panics on values above 21M BTC instead of returning an errorPosiblemente ocupada @bhuvan-somisetty la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
crate: spate-s3
Dificultad 2/5 Medio día Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
write_iceberg ignores the table's write.parquet.compression-codec propertyPosiblemente ocupada @YuangGao la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Eventual-Inc/Daft#7606 ·
Los mantenedores suelen responder en 1 día