InvalidArgument
status in apemanager
service
validateContainerTargetRequest
?
You can see it already wraps errors within
// validateContainerTargetRequest validates request for the container target.
// It checks if request…
Let me explain why this is barely possible and justify the current approach
At the same time we return this error too, so it may be handled twice.
ChainRouterError
won't be processed…
In your example it is logged, then returned (on the caller it can also be logged (again), then returned etc.).
I caught your idea for now. Yes, I agreed. This point is absolutely fair
TBH, stuffing error messages with so many details doesn't look reasonable for me.
@dkirillov wrote in TrueCloudLab/frostfs-node#1655 (comment):
LGTM, but what about container operations?
Added for container service
I have implemented an encoder for *apecommon.ChainRouterError
. Please, check.
I agreed with your suggestion