Trap candidate: event-timestamp-ns
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
First, find a public SDL3 port, commit, or issue that shows this timestamp bug and comment with the real code; the issue says work starts only after confirmation. Then read CONTRIBUTING.md’s “Adding a trap” instructions and copy the mouse-logical-coords fixture that pushes and polls events. Add the card to plugins/sdl3-porter/skills/sdl3-porter/references/events.md; done means fixtures pass CI on Windows, Linux, and macOS with SDL 3.2.0 and 3.4.18, and the candidate is removed from the README list.
Written by the indexing model from the issue text.
Description
What changed: SDL_Event's timestamp is now in nanoseconds, from SDL_GetTicksNS(). SDL2 code that compares it with SDL_GetTicks() or treats it as milliseconds is off by a factor of a million. (migration guide)
Why it's a candidate: it compiles cleanly and can be proven headless, but no port has shown it in real code yet. It becomes a trap, with fixtures and an eval case, when a port or an issue shows it. If your SDL3 port ran into it, comment with the code.
Taking it on: first comment with the real code that shows it: a public SDL3 port, commit or issue where it caused a bug. Once I confirm it qualifies, follow "Adding a trap" in CONTRIBUTING.md and copy mouse-logical-coords, the one fixture that pushes and polls events with SDL_PushEvent. The card goes in plugins/sdl3-porter/skills/sdl3-porter/references/events.md, which would get its first trap. The fixtures have to pass CI on Windows, Linux and macOS against SDL 3.2.0 and 3.4.18, and the PR removes the id from the README's list of candidates. I run the eval case myself, because evals use a repository secret.
- Dominant language
- C
- Stars
- 1
- Forks
- 1
- Avg merge
- 13m
- Merged PRs (30d)
- 3
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 hazeliscoding/sdl3-porter
-
trap-cards check: require every part of a trap cardPossibly taken A pull request linked to this issue is open or already merged. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hazeliscoding/sdl3-porter#20 ·
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
hazeliscoding/sdl3-porter#19 ·
-
Test find_traps.py's search of the committed SDL2 codePossibly taken @ian0318git claimed this 7 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
hazeliscoding/sdl3-porter#18 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
hazeliscoding/sdl3-porter#17 ·
-
trap-cards check: require a sample and an eval case for every trapPossibly taken A pull request linked to this issue is open or already merged. Openenhancement good first issue
Difficulty 3/5 1-2 days Newbie friendliness 82/100
hazeliscoding/sdl3-porter#21 ·
All issues in hazeliscoding/sdl3-porter
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ly05010419/MacNativeGames#1252 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Component - Build
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Lighthouse#655 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100