Effectively leverage typed errors by defining precise sealed hierarchy of errors
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- —
- 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:22 UTC
What the listing says
Ideally, we would have a sealed trait that defines every possible error that can result from JDBC, each as a case class that stores relevant context, including any underlying Throwable. The sealed trait should be engineered to group related exceptions into a finite number of logical categories. We need confidence that
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, 💎 Bounty
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