mirror of
https://github.com/nspcc-dev/neofs-sdk-go.git
synced 2026-03-01 04:29:18 +00:00
ObjectRangeInit does not return an error on an incorrect token verb #285
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#285
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 @tatiana-nspcc on GitHub (Nov 11, 2025).
Current Behavior
ObjectRangeInitreturns no error and an emptyObjectRangeReaderwhen an incorrect token verb is used.Expected Behavior
It should return a clear and understandable error.
Steps to Reproduce
I used a valid
PrmObjectRangewithVerbObjectGetinstead ofVerbObjectRange.@roman-khimov commented on GitHub (Nov 11, 2025):
Doesn't seem to be an SDK issue. Rather it's a node fallback, right, @carpawell, @cthulhu-rider? The question is if it's a feature or a bug. Refs or duplicates https://github.com/nspcc-dev/neofs-node/issues/3547.
@cthulhu-rider commented on GitHub (Nov 12, 2025):
most likely. But having
this can be considered legit for empty object only. Is this the case @tatiana-nspcc?
@tatiana-nspcc commented on GitHub (Nov 12, 2025):
No, the object wasn’t empty, I verified this using
ObjectGetInit, which returns the full object. It was 1000 randomly generated bytes.