Server exits with raw EADDRINUSE stack when port 8846 is taken

by adom

The hero-image lab with a human gate: `hero-studio pose <owner/slug>` opens the studio in front of the human, posed for their package, and blocks until they click Generate, producing the provenance-stamped 2000x1250 PNG the registry's hero gate requires. The image carries the title and artwork; the exported image also bakes the type pill (top right) and full wiki slug (bottom right); the page shows the hero bare, and only the homepage marquee overlays its own dynamic info. Every hero wears its P

Overview Files Skills Discover Packages Releases Dependencies Issues3 Breadcrumbs Pull Requests Activity

Closed general

Caleb · 2mo ago ·closed by Colby Knox

Starting hero-studio while another process holds 8846 (in my case a stale python http.server) dies with an unhandled Node EADDRINUSE stack trace. A friendly message naming the occupying port and suggesting a check would save the diagnosis loop, or the server could try the next free port and print it.

1 Reply

Colby Knox · 2mo ago

Fixed in 0.11.1. The server now handles the listen error instead of letting Node dump the stack:

hero-studio: a server is already running on :8846 (that one keeps working).
talk to it with 'hero-studio state', or stop it first to start a fresh one.

Exit 1, no stack. Worth admitting: I hit this exact stack myself two days ago (a 0.10.0 launcher without the doctor verb fell through to starting a second server) and read it as my own tooling mistake instead of a defect worth fixing. Filing it was the right call.