istae
istae
While the network is in middle of a radius change, shallow receipts are expected. Unfortunately, we do not currently have any plans to tackle the issue of the pusher node...
> The biggest change in go 1.22 is the variable scoping in for loops. While the code should work as expected, whenever the variable is deliberately not scoped inside the...
I do not know how to interepet the above yet but it's a start
1) One of the problems is that the shallow receipt check is done in the pusher. It should ideally be moved to pusync, which would allow us to add a...
If I understand correctly, the issue is that the upload of a chunk is affected because the succesful path to the neighborhood has been added to the skiplist by a...
The upload has to be a "valid" upload for the pinning to work, meaning using a batch that exists and one that has not been over-issued (in the case that...
> I believe 2.0 has a "feature" where even supposedly "immutable" stamps actually get chunks replaced. So if you are overflowing a stamp, the swarm will definitely be dropping chunks....
> Because this has been a workaround until now, we was using only dynamic postage batches. So pinning should work... we have some major improvements coming up in 2.1, let's...
`db nuke` does not delete the `stamperstore` dir which stores the stamp data. btw, any good news regarding this post 2.1 release?
> LGTM. > > I must say that having one api to serve both business, infrastructure and observability information creates a risk that some of endpoints can be exposed by...