HDegroote
HDegroote
I believe this is either a bug or an incorrect error message, it depends on whether the client is supposed to be usable for sharing hypercores which are neither hyperdrives...
The remote hypercores used in exercise 6, 8 and 14 are no longer being seeded, so these exercises cannot be completed. (see also https://github.com/hypercore-protocol/p2p-indexing-and-search/issues/5 ) I think this tutorial is...
Marked as draft because I'm not sure exactly which parts of the code related to batches were work-arounds and which were on purpose. Note in particular that I am now...
Something odd happens when a drive is closed before it has managed to complete `_openBlobsFromHeader` (for example because the drive is not yet available locally): - Old behaviour: `_close()` throws...
Currently `drive.put(...)` resolves to undefined. This makes it tricky to know at which exact version a file was added to the drive. Returning the version or the node which was...
It should be possible to load a drive in a different namespace of the same corestore. Currently this fails if the drive is loaded before the original drive's header was...
Current behaviour is a low-level error, even when the required block is available from the swarm and `core.length` is higher: ``` /home/hans/holepunch/hypercore/node_modules/random-access-memory/index.js:86 return req.callback(new Error('Could not satisfy length'), null) ^...
`this.contiguousByteLength` always returns 0. Removing the special-case on non-spareness fixes it