nspcc-dev/neofs-node

Unify status usage in storage engine when object is missing

オープン

#2,956 opened on 2024/10/01

 (0 件のコメント) (1 件のリアクション) (0 人の担当者)Go (49 件のフォーク)auto 404
I4S3U4enhancementgood first issue

Repository metrics

Stars
 (36 個のスター)
PR merge metrics
 (PR metrics pending)

説明

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.

コントリビューターガイド