client: `Get` and `GetRange` handlers miss some invalid messages sequences #255

New issue

Open

opened 2025-12-28 18:07:35 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:07:35 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 10, 2024).

Get(Range) response payload is defined as oneof, but messages must be streamed in a strict order:

all messages with chunk or
exactly one message with split_info field

Current Behavior

split_info after chunk -> split info error (Range)
chunk after split_info -> split info error

Expected Behavior

unexpected message instead of chunk part: *object.SplitInfo error
unexpected message after split info response error

Steps to Reproduce

corresponding tests from #641

Regression

Your Environment

Version of the product used: 335d9fe90f

Originally created by @cthulhu-rider on GitHub (Dec 10, 2024). `Get(Range)` response payload is defined as oneof, but messages must be streamed in a strict order: - all messages with `chunk` or - exactly one message with `split_info` field ## Current Behavior 1. `split_info` after `chunk` -> split info error (Range) 2. `chunk` after `split_info` -> split info error ## Expected Behavior 1. `unexpected message instead of chunk part: *object.SplitInfo` error 2. `unexpected message after split info response` error ## Steps to Reproduce * corresponding tests from #641 ## Regression no ## Your Environment * Version of the product used: 335d9fe90f24494944c2888ef385f06f5f81dcfc