PutSingle with OID that was already removed
headRequest -> [verifyResponse](https://git.frostfs.info/TrueCloudLab/frostf…
PutSingle with OID that was already removed
It looks really tricky, but any non-ObjectAlreadyRemoved-error is delegated to chunk processing to not break the Put logic.
The alternative way - to introduce a separate bucket for…
PutSingle with OID that was already removed
tombstones are created only for parent for EC objects.
That's why this change has been introduced.
ecWriter chunks EC-object and sends these parts down to engine through metabase.…
PutSingle with OID that was already removed
DeleteObject
@dkirillov correctly highlighted about local head-ing. It seems this is the only way is to force CheckAPE to fetch a full header. So, the third parameter (that's currently always true)…
As we're enhancing error messages, could you, please, also truncate error word from "... error: %w errors in non-cmd package?
Okay, let me clarify what I really meant:
errcan be assigned with context cancellation errors as context is propagated through functor but that may happen on stream opening, not on…
I suppose the context is going to be propagated through functor
err := p.requestWithRetry(ctx, prm.CID, func(client *rpcclient.Client) (inErr error) {
resp, inErr = rpcapi.Add(client,…Let me highlight some points about this method
It seems any error from ctx.Error() make any dialing call with ctx not redialable as ctx is already Done()
ctx.Error() != nil could be enough?