carpawell
carpawell
If small object bounds equal a range request bound, it led to [X:0] requests. Closes #2849.
It was not added in #1874 because it is still not clear how Tree service should share (and should it?) ACL rules with the object service.
## Is your feature request related to a problem? Please describe. I'm always frustrated when I know that a node responds with the first API (error) status it gets from...
## Is your feature request related to a problem? Please describe. We often do some caching and often use "10/64/100mb cache for \ at max is not bad" words and...
## Is your feature request related to a problem? Please describe. I'm always frustrated when we miss some details about meta when it [behaves badly](https://github.com/nspcc-dev/neofs-node/issues/2844). ## Describe the solution you'd...
## Is your feature request related to a problem? Please describe. I'm always frustrated when we use "dynamic" code. In the storage engine currently, we can accept any (non-empty) storage...
## Expected Behavior Metabase is asked to open bbolt in RO, and I expect the internal state to be RO too. ## Current Behavior Bbolt is opened in RO, however,...
## Is your feature request related to a problem? Please describe. I'm always frustrated when external test code cannot see what is happening in the storage engine. We need to...
## Expected Behavior Prioritized shards should be blocked until they are free or network timeout is reached. Do not break HRW rules just cause some shard is less loaded. ##...
## Is your feature request related to a problem? Please describe. GC may be more intelligent. Currently, it only works with clear wording like "a user deleted an object" or...