Why do you want to contribute?
I'd like to contribute small, well-scoped bug fixes to trigger.dev. My first proposed fix targets issue #3292 (OTLP nanosecond timestamp overflow) — a 4-line change across 3 files, plus a .server-changes/ entry. The PR was #3521 but was auto-closed pending a vouch (same as the prior community PRs #3378 and #3381 for the same issue).
The fix follows the exact pattern already used by convertDateToNanoseconds() in the same file (BigInt(ms) * BigInt(1_000_000) instead of BigInt(ms * 1_000_000)), preventing IEEE-754 precision loss for epoch-ns values that exceed Number.MAX_SAFE_INTEGER.
Prior contributions or relevant experience
GitHub: https://github.com/cybertron288
Happy to scope future contributions to similarly bounded, mechanical fixes.
Why do you want to contribute?
I'd like to contribute small, well-scoped bug fixes to trigger.dev. My first proposed fix targets issue #3292 (OTLP nanosecond timestamp overflow) — a 4-line change across 3 files, plus a
.server-changes/entry. The PR was #3521 but was auto-closed pending a vouch (same as the prior community PRs #3378 and #3381 for the same issue).The fix follows the exact pattern already used by
convertDateToNanoseconds()in the same file (BigInt(ms) * BigInt(1_000_000)instead ofBigInt(ms * 1_000_000)), preventing IEEE-754 precision loss for epoch-ns values that exceedNumber.MAX_SAFE_INTEGER.Prior contributions or relevant experience
GitHub: https://github.com/cybertron288
Happy to scope future contributions to similarly bounded, mechanical fixes.