closing a core, should make ALL errors coerce to SESSION_CLOSED

Open
#374 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Start by tracing the core closing path and how random-access-storage close errors are surfaced. Check where SESSION_CLOSED is defined or applied, then verify that every error produced during core shutdown is consistently exposed as SESSION_CLOSED.

Written by the indexing model from the issue text.

Description

Sometimes now its gives the random-access-storage close error which is confusing

Dominant language
JavaScript
Stars
2.9k
Forks
211
Avg merge
5h 49m
Merged PRs (30d)
9

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 holepunchto/hypercore

All issues in holepunchto/hypercore

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.