mirror of
https://github.com/nspcc-dev/neofs-sdk-go.git
synced 2026-03-01 04:29:18 +00:00
Slicer overrides object version #277
Labels
No labels
I2
I3
I4
S1
S2
S3
S4
U0
U1
U2
U2
U2
U3
U4
blocked
bug
client
config
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
performance
pool
question
security
task
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-sdk-go#277
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roman-khimov on GitHub (Jul 23, 2025).
Current Behavior
User can put any version into object header, slicer will ignore it and set whatever is the latest for it.
nspcc-dev/neofs-sdk-go@c7038b4506/object/slicer/slicer.go (L276-L277)Expected Behavior
Keep the original one, it's a part of the supplied header.
Possible Solution
Keep the version.
Steps to Reproduce
Lock S3 object with gateway 0.39.0 using NeoFS node 0.48.0. Lock object is specifically made to be compatible with 2.17, but NeoFS node overrides version and breaks object semantics.
nspcc-dev/neofs-s3-gw@f80abb1353/internal/neofs/neofs.go (L362-L363)Context
It's impossible to keep backwards compatibility this way. Old code creating objects the way that was correct previously stops working.
Regression
Doesn't look like, it was always this way.
Your Environment