ldeffenb
ldeffenb
### Context bee 1.6.2-684a7384 - but it has been happening for a long time now based on my anecdotal observations of pinned chunks being subsequently retrieved from the swarm. ###...
### Context bee 1.5.0rc3 89021656 on testnet under Windows ### Summary I have a large push queue waiting for a series of uploads. After finally successfully delivering a bunch of...
#### Summary I have a bee node with 150+GB of pinned content making the localstore bins quite full. I have noticed several times that my CPU consumption has pegged at...
### Context An existing testnet node with 70,000+ pinned chunks was upgraded to 1.5.0 rc1. Attempting to delete an existing pin hangs. ### Summary I decided to remove all of...
#### Summary I've had several times when /stewardship reports that a reference is retrievable, but yet a /bytes of that same reference from that same node fails. I finally tracked...
I've got a node.js script that uses bee-js's bee.downloadData extensively along with axios for /stewardship (until the pinning requirement is removed from bee-js). I noticed when running against a bee...
### Context 1.18.2 on goerli testnet ### Summary I have a testnet node that has had this stamp for some time now: ``` "stamps": [ { "batchID": "45ef9e72cad000467d828bd82b769f63ff848f216013c1866c0270533bc879e3", "utilization": 49,...
The Readme specifies the minimum bee version as `Bee version 1.12.0-88c1d236`. Somehow I think it really doesn't work with a bee node that old?
The readme specifies a minimum bee version as `Bee version 1.9.0-13a47043`. I suspect swarm-cli really needs a bee newer than that?