Skip to content
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

The first child in the Slicer's chain is always "user's object" #448

Closed
notimetoname opened this issue Jun 9, 2023 · 0 comments · Fixed by #463
Closed

The first child in the Slicer's chain is always "user's object" #448

notimetoname opened this issue Jun 9, 2023 · 0 comments · Fixed by #463
Assignees
Labels
bug Something isn't working
Milestone

Comments

@notimetoname
Copy link
Contributor

Slicer always writes the first object in a chain with an empty split field. Such an object does not differ from a user object at all (e.g. it can be found with the --raw flag in neofs-cli).
#427 fixes all the other objects in a chain but not the first one. It can not be fixed with a single hotfix line, it is broken by design. Must be done carefully.

@notimetoname notimetoname added the bug Something isn't working label Jun 9, 2023
@roman-khimov roman-khimov added this to the v1.0.0-rc10 milestone Jun 13, 2023
@smallhive smallhive self-assigned this Jul 5, 2023
smallhive added a commit that referenced this issue Jul 6, 2023
closes #448

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
smallhive added a commit that referenced this issue Jul 6, 2023
closes #448

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
smallhive added a commit that referenced this issue Jul 7, 2023
closes #448

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants