Run search: relative time shows ~5 hours ago for freshly uploaded runs (timezone parsing)
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 30
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 6
Description
Bug: Newly uploaded content shows “5 hours ago” instead of “just now” (timezone parsing)
Summary
On the search results page (e.g. runs), newly uploaded items can display a relative time like “5 hours ago” even when they were uploaded just now. This affects users in IST (UTC+05:30) and likely any non-UTC timezone.
Where it happens
- URL example: https://www.openml.org/search?type=run&sort=date&uploader_id=%3D_55151
- Frontend file:
server/src/client/app/src/pages/search/SearchResultsPanel.js - Code currently does:
<TimeAgo date={new Date(this.props.date)} minPeriod={60} />
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with server/src/client/app/src/pages/search/SearchResultsPanel.js and reproduce the issue from the provided search URL using a non-UTC timezone such as IST. Inspect how the date prop is passed to TimeAgo and verify the behavior for a freshly uploaded run. Done means newly uploaded results show “just now” rather than several hours ago across timezones.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100