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

[commandline] servers seem not to block waiting for connections

Open
#85 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
backend

Research direction

Reproduce the issue using the listed snap checkout, fallthrough branch, sandbox setup, and dist/build/demo/demo -p 8000 command. Start at the quickServe example and commandline branch, then verify that the demo process stays running and produces the expected access.log or error.log output.

Written by the indexing model from the issue text.

Description

I'm working on the commandline branch. A simple example server such as the one below prints the typical snap startup info to stdout, and then the process immediately ends without writing anything to access.log or error.log:

main = quickServe (writeText "hello")

Steps to reproduce:

  1. git clone git@github.com:imalsogreg/snap
  2. cd snap
  3. git checkout origin/fallthrough
  4. git submodule update --init --recursive
  5. ./init-sandbox.sh
  6. cabal install --only-dep
  7. cabal build
  8. dist/build/demo/demo -p 8000
Dominant language
Haskell
Stars
197
Forks
87
No merged PRs in 30d

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.

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.