FSTree `io.Seeker` behavior #1522

New issue

Open

opened 2025-12-28 17:35:43 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:43 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Oct 13, 2025).

Looks like we need to specify that fstree seekers use payload beginning for 0. Which makes total sense, but this needs to be ensured for all cases then.

Originally posted by @roman-khimov in https://github.com/nspcc-dev/neofs-node/pull/3600#discussion_r2426716841

lets:

doc io.Seeker interface of https://pkg.go.dev/github.com/nspcc-dev/neofs-node/pkg/local_object_storage/blobstor/fstree#FSTree.GetStream
cover all cases in unit tests

consider:

declare io.ReadSeekCloser return to not dynamically try io.Seeker on caller side

refs #3593

Originally created by @cthulhu-rider on GitHub (Oct 13, 2025). Looks like we need to specify that fstree seekers use payload beginning for 0. Which makes total sense, but this needs to be ensured for all cases then. _Originally posted by @roman-khimov in https://github.com/nspcc-dev/neofs-node/pull/3600#discussion_r2426716841_ lets: - doc `io.Seeker` interface of https://pkg.go.dev/github.com/nspcc-dev/neofs-node/pkg/local_object_storage/blobstor/fstree#FSTree.GetStream - cover all cases in unit tests consider: - declare `io.ReadSeekCloser` return to not dynamically try `io.Seeker` on caller side refs #3593