Undefined behaviour when original postage stamp has expired and using the stewardship endpoint

[Cafe137]

We will keep retrying the reupload, resulting in an endless error spam, and consequent healthy pins may never get reuploaded because of this.

We should advise to use the TTL extend stamp strategy in conjunction with the content reupload feature anyway, but a real fix would be support for restamping the content in Bee

[Cafe137]

What makes it worse is the issue ethersphere/bee#3302 which makes it impossible to unpin stuff, so the error cannot be escaped

[Cafe137]

ethersphere/bee#3541

[ldeffenb]

What makes it worse is the issue ethersphere/bee#3302 which makes it impossible to unpin stuff, so the error cannot be escaped

Well, if you really want to brute force it, and have a way to identify all of the individual chunks involved in a reference (like verbose bee node logs), you can use the -X DELETE /chunks API to completely remove chunks from your local node, regardless of their pinning status. But this works one chunk at a time as the API name implies.