Investigate and remove util.ErrAbortStream #1664

Open
opened 2025-03-06 11:22:00 +00:00 by fyrchik · 0 comments
Owner

It was introduced in 7f5fb130c0 (diff-f9fb9a9419164dc9a10f6de9003e9b0d771cfa48)
And it seems we use it to treat signature error as a status error.
The question is: can this be achieved in a different way?

Originally posted by @fyrchik in #1659 (comment)

It was introduced in https://git.frostfs.info/TrueCloudLab/frostfs-node/commit/7f5fb130c006337de41e5b141d8861bdb581a2d4#diff-f9fb9a9419164dc9a10f6de9003e9b0d771cfa48 And it seems we use it to treat signature error as a status error. The question is: can this be achieved in a different way? _Originally posted by @fyrchik in https://git.frostfs.info/TrueCloudLab/frostfs-node/pulls/1659#issuecomment-69476_
fyrchik added the
frostfs-node
help wanted
good first issue
refactoring
labels 2025-03-06 11:22:24 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#1664
No description provided.