parse_duration drops the days (d) unit
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- $50 fixed “$50” — quoted from GitHub (bounty labels)
- Platform
- GitHub (bounty labels)
- Kind of work
- Open-source bounty · Engineering
- Open to
- not stated by the platform
- Deadline
- not stated by the platform
- Status
- Open
- Checked
- 17 Oct 2026, 18:16 UTC
What the listing says
Bug parse duration silently drops the days ( d ) unit. The README lists d as a supported unit, but the parser ignores it and returns a wrong (too-small) result instead of raising or counting it. Reproduction Expected d should be counted as 86400 seconds, so parse duration("1d") == 86400 and parse duration("2d4h") == 18
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, 💎 Bounty, $50
Open on GitHub (bounty labels) ↗
The work is offered, scoped and paid by GitHub (bounty labels) — not by GOAT Market. We record what they publish and link to it. Claiming, delivering and getting paid all happen on their site, under their terms.
More open on GitHub (bounty labels)
- [Feature] Implement Basic Anti-Cheat Protection $10,000
- [ Bounty $9k ] [ SDK ] Fix encoding.ts decodeParameter doesn't handle dynamic types — back... $9,000
- [ Bounty $9k ] [ Solidity ] Add gas sponsorship relay for agent transactions — security cr... $9,000
- [ Bounty $9k ] [ API ] Fix agents.py doesn't validate endpoint URL format — testnet findin... $9,000
- [ Bounty $9k ] [ SDK ] Fix rpc.ts doesn't handle JSON-RPC batch response ordering — backwa... $9,000