nrepl / nrepl/weasel

Detect cider-disconnect, close listen-socket

Open
#52 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
323
Forks
31
PR merge metrics
No merged PRs in 30d

Description

If you have a weasel-repl open and kill emacs (or close the repl buffer) then the listen-socket for the websocket connection stays open, leading to a BindException: Address already in use.

A new weasel-repl should either use an already existing socket (if that's possible) or close other ones automatically.

If #51 implements close-on-disconnect we could implement it for the other direction too.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issue #51 and tracing the websocket listen-socket lifecycle for a weasel-repl. Reproduce the sequence of killing Emacs or closing the repl buffer, then verify that opening a new repl no longer produces BindException: Address already in use, either through socket reuse or cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.