ceramicnetwork / ceramicnetwork/js-ceramic
libp2p stream reset error
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 126
- PR merge metrics
- No merged PRs in 30d
Description
Haven't figured out how to replicate this yet, but it seems to happen pretty frequently when running Ceramic-cli v0.13.3. It seems like it might cause the daemon to not respond to requests? Not sure yet, but wanted to put it on your radar because it will break any app that is doing simple ceramic operations.
```
(node:46818) UnhandledPromiseRejectionWarning: Error: stream reset
at Object.reset (/Users/jonathanschwartz/Documents/owl/streams/streams-js-tooling/apps/streams-api/node_modules/libp2p-mplex/src/stream.js:72:27)
at Mplex._handleIncoming (/Users/jonathanschwartz/Documents/owl/streams/streams-js-tooling/apps/streams-api/node_modules/libp2p-mplex/src/mplex.js:227:16)
at /Users/jonathanschwartz/Documents/owl/streams/streams-js-tooling/apps/streams-api/node_modules/libp2p-mplex/src/mplex.js:156:22
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Mplex.sink (/Users/jonathanschwartz/Documents/owl/streams/streams-js-tooling/apps/streams-api/node_modules/libp2p-mplex/src/mplex.js:149:9)
(Use `node --trace-warnings ...` to show where the warning was created)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running Ceramic-cli v0.13.3 and investigate the reported unhandled rejection. The only location shown is the installed libp2p-mplex code in node_modules/libp2p-mplex/src/stream.js and src/mplex.js; done means reproducing the stream reset and determining whether it makes the daemon stop responding to Ceramic operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100