Final submitted code is not preserved in Past attempts reports
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by tracing the interview submission flow into the generated report, focusing on the Your final code (C) section and the (final code was not saved) fallback. Reproduce the issue with a C coding interview, then verify that the submitted final code appears in the report for each stated interview outcome.
Written by the indexing model from the issue text.
Description
Update after retesting
After retesting, I confirmed that the report shown immediately after the interview correctly preserves the final submitted code.
The code is only missing after returning to the lobby and reopening the same interview from Past attempts.
In that case, the reopened report shows:
Your final code (C)
(final code was not saved)
Therefore, this issue is better treated as a request to preserve the final submitted code in interview history, rather than a bug in the immediate post-interview report.
Steps to reproduce
- Complete a coding interview with code in the editor.
- Confirm that the report shown immediately after the interview contains the final code.
- Return to the lobby.
- Open the same interview from Past attempts.
- Scroll to
Your final code (C).
Current behavior
The reopened report shows:
(final code was not saved)
Requested behavior
Preserve the final submitted code in interview history so that reports reopened from Past attempts can still display it.
- Dominant language
- Rust
- Stars
- 160
- Forks
- 64
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 114
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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
-
Highlight the active line in the code editorPossibly taken @ArthurArthurArthur0817 claimed this 8 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sysprog21/codetrial#247 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Include local time in downloaded report filenamesPossibly taken @106081011 claimed this today. Open
sysprog21/codetrial#309 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Avoid automatic bracket pairing inside comments and stringsPossibly taken @Jonathas2127 claimed this 1 day ago. Open
sysprog21/codetrial#307 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
Preserve test run historyPossibly taken @yunhsuan0510 claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 62/100
sysprog21/codetrial#301 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in sysprog21/codetrial
Similar issues
-
agent:triaged bug bughunt pm:bundler priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SocketDev/socket-patch#1573 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
bytecodealliance/rustix#1706 · 1 comment ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wormhole-foundation/wormhole#5062 ·
Maintainers usually reply within 1 day
-
LaunchOrFocusPlugin switches to the wrong tab after tabs are reordered (tab id used as position)Possibly taken @olegator888 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zellij-org/zellij#5719 ·
Maintainers usually reply within 1 day