Status for already removed container #139

New issue

Open

opened 2025-12-28 18:12:42 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:12:42 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 23, 2025).

Container contract supports the exception since https://github.com/nspcc-dev/neofs-contract/pull/404. Once container is removed, it becomes inoperable. This fact would be nice to be highlighted in responses

Describe the solution you'd like

add CONTAINER_ALREADY_REMOVED status

Originally created by @cthulhu-rider on GitHub (Dec 23, 2025). ## Is your feature request related to a problem? Please describe. similar to https://github.com/nspcc-dev/neofs-api/blob/fc8584b766d6b544337fc055dca34c29b0155d31/status/types.proto#L137-L138 Container contract supports the exception since https://github.com/nspcc-dev/neofs-contract/pull/404. Once container is removed, it becomes inoperable. This fact would be nice to be highlighted in responses ## Describe the solution you'd like add `CONTAINER_ALREADY_REMOVED` status

sami added the

feature

labels

2025-12-28 18:12:42 +00:00

sami commented

2025-12-28 18:12:42 +00:00

Author

Owner

@roman-khimov commented on GitHub (Dec 23, 2025):

Not hard to do, but when do we care about the difference?

@roman-khimov commented on GitHub (Dec 23, 2025): Not hard to do, but when do we care about the difference?

sami commented

2025-12-28 18:12:42 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Dec 23, 2025):

while managing eACL or attributes, for example

in practice, 404 is mostly caused by mistake in ID. More specific case is parallel creation and management transactions

at the same time, "already removed" would mean "🛑 working with this container". It seems more representative to me

@cthulhu-rider commented on GitHub (Dec 23, 2025): while managing eACL or attributes, for example in practice, 404 is mostly caused by mistake in ID. More specific case is parallel creation and management transactions at the same time, "already removed" would mean "🛑 working with this container". It seems more representative to me