ldeffenb
ldeffenb
### Context 2.0.0 ### Summary While investigating a reduction in pullsync rates filling the reserve in a brand new node, I looked at the source and found the pullsync rate...
### Context 2.0.0 ### Summary I'm uploading a lot of files using the /bytes API with deferred and pin options. I noticed in the --verbosity 5 logs that the pusher...
### Context 2.0.0 ### Summary While uploading with deferred, pinned uploads using the /bytes API, I see the following log: ``` "time"="2024-04-03 15:06:18.444457" "level"="error" "logger"="node/pusher" "msg"="pusher: failed reporting chunk" "error"="reporter.Report:...
### Context Bee 2.1.0 (and earlier) ### Summary Related to #4703 Pullsync only pulls chunks that are not already in the reserve based solely on address and batch. If content...
### Context 2.1.0 (and possibly earlier) ### Summary I am re-uploading existing data on an existing stamp to the swarm. The pushing stamper updates the existing stamp's timestamp in this...
### Context 2.1.0 ### Summary I'm trying to evaluate the impact of including redundancy on the next version upload of the OSM dataset which is very heavy with single chunk...
### Context 2.1.0 (and all earlier, I suspect) ### Summary I have a file reference on the swarm mainnet that is missing a chunk, but yet the /stewardship API insists...
### Context v2.1.0 (and earlier) ### Summary Several of my sepolia testnet nodes are not participating in the storage compensation rounds. All of these nodes have storage radius 4 while...
### Checklist - [x] I have read the [coding guide](https://github.com/ethersphere/bee/blob/master/CODING.md). - [x] My change requires a documentation update, and I have done it. - [x] I have added tests to...
### Context v2.1.0 on sepolia testnet swarm ### Summary I had 13 nodes running on a single host, 2 on an internal NVME SSD and the other 11 on a...