-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complex object is completely unreadable after upgrade to SDK RC-9 #2448
Comments
i have not seen |
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
|
Do I understand correctly that we can't release node with SDK RC9 and we definitely need RC10 for everything to work correctly? |
Fixed by #2470? |
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: