magic-wormhole / magic-wormhole/fowl

factor "shutdown" flow into one place

Open
#52 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
163
Forks
14
Avg merge
14h 58m
Merged PRs (30d)
3

Description

If the "nice shutdown" flow actually works well, factor it into `FowlWormhole.close_wormhole` (or similar). If it doesn't (or if it goes in magic-wormhole itself) then delete it.

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 locating the existing "nice shutdown" flow and `FowlWormhole.close_wormhole`. Trace whether that flow works correctly here or belongs in magic-wormhole, then compare the relevant shutdown behavior before choosing a direction. Done means the working shutdown path is centralized in `close_wormhole`, or the unused flow is removed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.