You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If ants pool is busy and cannot take task, early `return` without `wg.Wait()`
leads to `iterateNodesForObject`'s `return` and all the buffers for binary
replication from now may be reused while are still in use by the other routines
inside the pool. Wait for WG before any `return` is called. Closes#2978, #2988,
#2975, #2971.
Signed-off-by: Pavel Karpy <[email protected]>
If ants pool is busy and cannot take task, early `return` without `wg.Wait()`
leads to `iterateNodesForObject`'s `return` and all the buffers for binary
replication from now may be reused while are still in use by the other routines
inside the pool. Wait for WG before any `return` is called. Closes#2978,
closes#2988, closes#2975, closes#2971.
Signed-off-by: Pavel Karpy <[email protected]>
This one is the only I'm not sure about wrt #3027. The behavior manifested here is rather strange and --binary only affects client side (interpreting the result). At the same time, we've not seen anything like that after patching 43.
Expected Behavior
if I have put an object, then fount oid using search I am able to head it.
Current Behavior
no deletion was performed in this container.
Context
I uploaded an object with an empty payload and now I want to head it.
The text was updated successfully, but these errors were encountered: