Fix Patch
handler bugs #1338
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1338
Loading…
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-node:fix/patch/3"
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?
Patch
handler: handle specific range with.offset = payload_length
andlength = 0
Patch
handler@ -204,7 +204,7 @@ func (a *auditPatchStream) CloseAndRecv(ctx context.Context) (*object.PatchRespo
if err != nil {
a.failed = true
}
a.objectID = resp.GetBody().ObjectID
I am wondering why
protogetter
linter hasn't catched this.@ -32,1 +34,4 @@
func (r *rangeProvider) GetRange(ctx context.Context, rng *objectSDK.Range) io.Reader {
// Remote GetRange request to a container node uses an SDK-client that fails range validation
// with zero-length. However, from the patcher's point of view, such request is still valid.
if rng.GetOffset() == r.originalPayloadLength && rng.GetLength() == 0 {
if rng.GetLength() == 0
, we don't care what the offset is, could just returnnopReader
, right?You're right. Fixed
aa602c36d8
toaaa7b7238e
aaa7b7238e
to6488ddee88