Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show local time in past attempt labels

Open Beginner friendly
  • Is something wrong?
#317 2 comments 1 reaction 1 assignee View on GitHub

Maintainers usually reply within 1 day

@jin11109 is already working on this.

Since Oct 15, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

The bug is in renderAttemptHistory in web/app.js, which formats each past attempt's label with toLocaleDateString() even though the attempt keeps its timestamp. Read that function, then the browser regression test that covers account and device history with newest-first labels. Done when the labels include local time, the UTC case that falls on the next local date passes, and the lobby tests pass.

Written by the indexing model from the issue text.

Description

Past attempts shows only the date in each row label. Two interviews completed on the same day with the same problem, language, and verdict therefore have identical labels, making it difficult to choose the intended report.

I reproduced this on main at 6b6cdfe using synthetic history in Chromium with the Asia/Taipei time zone and en-US locale. Attempts saved at 2026-01-01T16:15:00Z and 2026-01-02T10:30:00Z both display "1/2/2026 · Same problem · Python · HIRE". The expected labels include their local times, 12:15:00 AM and 6:30:00 PM.

The cause is renderAttemptHistory in web/app.js, which uses toLocaleDateString() even though each attempt retains its timestamp. A local proof of concept uses toLocaleString(), matching the date and time format already used by the Download report accessible names. PR #313 addresses downloaded filenames; this proposal only changes the visible history labels.

The browser regression test covers both account history and device history, checks newest-first labels, and includes a UTC timestamp that falls on the next local date. Both cases failed before the fix. After the fix, all 139 lobby tests passed with no skips. The source build and full test gate are still being checked; I am not claiming they pass.

Dominant language
Rust
Stars
160
Forks
64
Avg merge
1d 10h
Merged PRs (30d)
116

Getting set up

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.