lambdaisland / lambdaisland/kaocha-cljs2
Kaocha-cljs2 appears to hang when no clients connect
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 34
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
If no chui-remote clients are connected, Kaocha will wait forever. You can configure a timeout, but it's not enabled by default.
This is technically correct behavior and thus, arguably, not a true hang (which implies a deadlock or other invalid state), but it isn't very friendly to people setting it up for the first time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified. Start by tracing Kaocha-cljs2's handling of chui-remote client startup and the existing timeout configuration; clarify the intended default behavior before changing it. Done should include coverage showing that a run with no connected clients no longer waits forever by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100