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

Assist with core.async debugging

Open
#36 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
clojure
Domain
devtools

Research direction

Start by reviewing the proposed core.async sidebar in the Sources panel and the debugging capabilities it would require. Define the scope for listing go blocks, parked locations, and channel state, then identify what a workable fork and completion criteria would be before implementation.

Written by the indexing model from the issue text.

Description

enhancement

I can imagine implementing "core.async" sidebar pane on Sources panel.

When stopped on a breakpoint this pane would list all existing go blocks and their state (running/how they are parked). One could click on them to see the source code location where given go block is being parked.

Another feature could be better presentation of channels. Custom formatter could display all pending puts and takes on given channel, also it could display state of associated buffer.

This would require a fork of core.async with added debugging capabilities.

Dominant language
Clojure
Stars
775
Forks
29
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 binaryage/dirac

All issues in binaryage/dirac

Similar issues

More Clojure issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.