mafintosh / mafintosh/hyperlog
Uncaught Error: write after end
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 469
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I have tried to replicate my log using
``` peer.pipe(log.replicate({ live: true })).pipe(peer);```
But get the following error
```index.js:2568 Uncaught Error: write after end
at writeAfterEnd (index.js:2568)
at Encoder.Writable.write (index.js:2612)
at Protocol._encode (index.js:6257)
at Protocol.node (index.js:6231)
at index.js:6362
at index.js:5650
at index.js:8591
at index.js:4520
at index.js:7772
at IDBTransaction.transaction.oncomplete (index.js:7745)```
I was following the video on
https://www.elastic.co/videos/building-distributed-offline-website-by-mathias-buus
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
Start by reproducing the reported `peer.pipe(log.replicate({ live: true })).pipe(peer)` flow and inspect the stack in index.js, especially Protocol._encode, Encoder.Writable.write, and the IDBTransaction completion handler. Compare the behavior with the linked video and establish the conditions that cause the write-after-end error; done means the reproduction no longer fails or the remaining incompatibility is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100