Skip to content

[bug] WebSocket connections not cleaned up #528

Open

Description

@ritaifeoluwa

Problem

WebSocket connections aren't cleaned up when clients disconnect.

Impact

  • Memory leaks
  • Resource exhaustion
  • Poor reliability

Fix

Clean up disconnected WebSocket connections.

Location

src/websocket/

Activity

  1. Ranjeet2063 commented on Oct 17, 2026

    @Ranjeet2063

    Hello maintainers,

    I reviewed the requirements for "[bug] WebSocket connections not cleaned up" and would like to work on this implementation.

    I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.

    I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.

    Thank you!

  2. yodakkak commented on Oct 18, 2026

    @yodakkak

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

    I have implemented a WebSocket connection manager in src/ws/connectionManager.js (attachManagedSocket, unsubscribeSocket, cleanupSocket, sweepDeadClients, closeAllSockets) to remove event listeners, clear topic subscriptions, and terminate dead sockets on disconnect. Verified locally with unit tests; holding the PR branch privately until Drips Wave assignment so it is not merged unassigned—ready to push and open PR immediately upon assignment!

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

  3. ogundelevictory commented on Oct 18, 2026

    @ogundelevictory
    Contributor

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

    Hi there, i would like to fix this, kindly assign

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

  4. drips-wave commented on Oct 19, 2026

    @drips-wave

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

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

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

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programbugSomething isn't workingperformancePerformance improvements

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions