LeL

> #2480, whoops. Close or treat as a sub-part. this issue a little wider, so lets keep both

> Even if you get this additional data, there is not a lot you can do Best-effort - yes it is, but client needs to understand how it ended. Being...

> any GET/PUT operation should fixed then too @carpawell pls clarify what fix r u talking about? `GET`/`PUT` cannot fin with partial success lets focus on proposed expected behavior of...

@carpawell ur talking about clatification of failure responses while this issue is about partially succeeded ones. Neither `PUT` nor `GET` can end with partial success now. Different topics to me...

> GET and PUT can also be partially successful gotcha, i should've been clarify that under "partial success" i mean details of the scenario described in this issue. Lets stick...

> Need for what? for this issue to be resolved

i think it maybe really useful when timeout defaults with set `--timeout` flag, i don't think additional request justifies itself: network resources are spent only for writing a warning. IMO...

i restored how we came to this static sessions currently make no sense for `object put|delete|lock` commands according to [docs](https://github.com/nspcc-dev/neofs-node/blob/master/docs/cli-sessions.md#object) (code follows) once #1216 happened and we optimized dynamic sessions:...

We can start by getting the number of nodes in the network map at the specified epoch. * inspired by https://github.com/nspcc-dev/neofs-node/issues/1755 It may also be useful to check the presence...

lets postpone this issue a bit, several more fundamental optimizations are coming with [v0.40](https://github.com/nspcc-dev/neofs-node/milestone/56). It'd better to intro current optimization above those ones