Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

exception escaped to toplevel

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell

Research direction

Start with the websockets-snap server path that handles recv when the network connection resets. Reproduce the failure with Wi-Fi disabled and inspect how the exception reaches the toplevel and whether cleanup runs. Done means the behavior is defined for this recv failure and cleanup is verified, but the report names no files or tests.

Written by the indexing model from the issue text.

Description

I was running a websockets-snap server on my laptop,
when my wifi was off, I got

[24/Apr/2014:15:15:54 +0800] ["192.168.1.204"]: an exception escaped to toplevel: recv: resource vanished (Connection reset by peer)

and some clean up cannot executed,

is this a bug of snap-server?
should snap-server catch recv exception?

Dominant language
Haskell
Stars
197
Forks
87
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from snapframework/snap-server

All issues in snapframework/snap-server

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.