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
as opposed to access problem from another issue, here node can't even reach the fact that requested object is complex (virtual). I guess the problem may be in status codes and/or SDK client errors
i guess i found the reason: parent header contains split ID (slicing mistake) while it shouldn't. It's not obvious why metabase fails due to this, need to explore separately. If node considers such objects as problem, then it must deny them on PUT stage. I'll create an issue
i made same actions but with later NeoFS revision, but the result is completely different
all nodes respond with
log:
as opposed to access problem from another issue, here node can't even reach the fact that requested object is complex (virtual). I guess the problem may be in status codes and/or SDK client errors
Versions
18e3f68106f4e9d5f5ecda8f4b1caef74358be55
(not yet released)The text was updated successfully, but these errors were encountered: