Skip to content

PREWAVE-BE-057 — Implement Graceful Shutdown Across HTTP, Workers, Streams, and Database #654

Closed

Description

@dDevAhmed

Problem context

Source audit identified this distinct API production-readiness boundary.

Technical scope

Stop admission, drain bounded work, checkpoint consumers, close sockets/queues/Redis/DB, and exit with evidence.

Required tests

SIGTERM at each operation phase, timeout, stuck worker, WebSocket drain, and repeated signal tests.

Acceptance criteria

  • No new work starts after drain begins.
  • In-flight work completes or remains retryable.
  • Shutdown is time-bounded.
  • No handles/locks leak.

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.

Dependencies

Non-goals

Unrelated work, mainnet deployment, or applying Stellar Wave before maintainer activation.

Complexity and points

  • High — 200 points

Candidate only; activation remains maintainer-controlled.

Activity

  1. Hunterly01 commented on Oct 15, 2026

    @Hunterly01
    Contributor

    @Hunterly01 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I’d like to contribute to this issue and work on a solution. Kindly assign it to me

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hunterly01 to this issue.

  2. drips-wave commented on Oct 16, 2026

    @drips-wave

    Congratulations, @Hunterly01! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @Hunterly01: 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 🌊

  3. drips-wave commented on Oct 19, 2026

    @drips-wave

    This issue has been completed by @Hunterly01 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Hunterly01: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions