Chain as a part of frostfs-api
@fyrchik wrote in TrueCloudLab/frostfs-node#1638 (comment):
Private access rules may be a feature.
I suppose such way for listing doesn't violate…
Let's avoid using can't and failed in error messages. I used to use them too but actually that's unnecessary.
If request sets oid with an invalid format, then we can set codes.InvalidArgument instead of codes.Internal. Thus, a client won't retry GetShardByObjectID on invalid data :)
https://github.com/uber-go/goleak
But I don't think we are going to introduce a new import. I'd use the same idea like you with runtime :)
I can't figure out what is going on in this part. Why do you set a key to subject's KV storage and then remove it if disable flag is set? I checked the contract's method and deleteSubjectKV literally means deletion but not disabling.