nspcc-dev/neofs-node

Unify status usage in storage engine when object is missing

開放

#2,956 建立於 2024年10月1日

 (0 則留言) (1 個反應) (0 位負責人)Go (49 個分叉)auto 404
I4S3U4enhancementgood first issue

倉庫指標

星標
 (36 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

Is your feature request related to a problem? Please describe.

I'm always frustrated when we have both bool flags that mean the presence of an object in the engine and ErrObjectNotFound. Sometimes it is a flag and sometimes it is an error.

Describe the solution you'd like

It should either be error, or be a flag.

Describe alternatives you've considered

-

Additional context

Sometimes it is ok to have an error and sometimes we only accept a flag, it is unreliable. As for me, I wouldn't say I like using client statuses (that is where they are placed in SDK) in engines at all.

貢獻者指南