Reuploading content without increasing bucket collision counters, used stamp collision refinement

[metacertain]

Summary

Using direct uploads and potentially other use-cases (stewardship?), the exact chunks already uploaded included in the bucket collision counter are not remembered, so if a batch is used for reuploading the same data, the collision count can potentially be incremented multiple times for the same chunk

Motivation

Correctness

Implementation

To be verified, redesigned

Drawbacks

Introduces some overhead

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.

[ldeffenb]

Would this happen if the content was pinned or otherwise still present in the uploading node?