You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PREWAVE-BE-056 — Set Database Pool, Statement, and Transaction Budgets #649
Source audit identified this distinct API production-readiness boundary.
Technical scope
Define pool size, acquisition timeout, statement timeout, idle transaction timeout, and per-workload limits.
Required tests
Pool exhaustion, slow query, leaked transaction, shutdown, failover, and burst tests.
Acceptance criteria
Requests cannot exhaust the pool indefinitely.
Timed-out work is cancelled/rolled back.
Metrics are bounded and sanitized.
Background jobs have separate budgets.
Constraints
Canonical finalized contract events remain authoritative. Bind chain data to chain/release/artifact provenance; fail closed on stale, ambiguous, unauthorized, or incomplete state. Do not weaken CI or expose secrets/protected data.
Congratulations, @Starlitecrypto! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Starlitecrypto: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @Starlitecrypto: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
Songu3020 commentedon Oct 15, 2026
@Songu3020 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Songu3020 to this issue.
Starlitecrypto commentedon Oct 15, 2026
@Starlitecrypto has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Starlitecrypto to this issue.
drips-wave commentedon Oct 16, 2026
Congratulations, @Starlitecrypto! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Starlitecrypto: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
PREWAVE-BE-056: Set database pool, statement, and transaction budgets (…
PREWAVE-BE-056: Set database pool, statement, and transaction budgets (…
drips-wave commentedon Oct 19, 2026
This issue has been completed by @Starlitecrypto as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Starlitecrypto: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.