nspcc-dev/neofs-node
`neofs-cli` default timeouts for `object put`/`object get`/etc are implicit
Open
#2,393 opened on Jun 19, 2023
I3S4U3discussionhelp wantedneofs-cli
Repository metrics
- Stars
- (36 stars)
- PR merge metrics
- (PR metrics pending)
Description
After https://github.com/nspcc-dev/neofs-node/pull/2135 a user can see the following (15-sec default timeout that did not exist before):
▶ neofs-cli object put -r s01.neofs.devenv:8080 -w services/chain/node-wallet.json --cid HrG4qXKc3fpvY1dBay4Jy4qtDgGbwEnDtikDUJTegZJi --file tmp/test.file
Enter password >
276824064 / 10000000000 [=======>-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 2.77% 12s
rpc error: client failure: rpc error: code = DeadlineExceeded desc = context deadline exceeded
as a user, I would ask some questions:
- "rpc error:"? Really? Network error? The node is down?
- I have the progress bar, I see how it works and nothing is frozen, I control it and can send SIGINT if I want to. Why 15-sec timeout is forced? "Any object should be put in 15 seconds" is smth unnatural for a util (at least by default when a progress bar is active).
- Why doesn't it work the same as
wget/curl?
cc @532910, @MaxGelbakhiani, @aprasolova, @vvarg229