search

near / near-cli-rs

near CLI is your human-friendly companion that helps to interact with NEAR Protocol from command line.
https://near.cli.rs
Apache License 2.0
98 stars 55 forks source link

Issues with staking to the pool #307

Closed telezhnaya closed 7 months ago

telezhnaya commented 7 months ago

Hey! I tried to stake through the cli and it crashed.

% near
> What are you up to? (select one of the options with the up-down arrows on your keyboard and press Enter) staking     - Manage staking: view, add and withdraw stake
> Select the type of stake: delegation       - Delegation management
> Enter the account that you want to manage delegated stake for: my-account.near
> Select actions with delegated staking: stake                - Delegate a certain amount of previously deposited or unstaked NEAR tokens to a validator's staking pool
> Enter the amount to stake from the inner account of the predecessor (example: 10NEAR or 0.5near or 10000yoctonear): N NEAR
> What is delegated validator account ID? some-pool.poolv1.near
> What is the name of the network? mainnet

And right after that, it crashed

The application panicked (crashed).
Message:  called `Result::unwrap()` on an `Err` value: Error("number out of range", line: 0, column: 0)
Location: /Users/olgatelezhnaya/.cargo/registry/src/index.crates.io-6f17d22bba15001f/near-cli-rs-0.7.7/src/commands/staking/delegate/stake.rs:37

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

After this, I provided absolutely same arguments through 

near transaction construct-transaction ... deposit_and_stake ...

And I actually had the second issue - endless repeats of timeouts

Transaction sent ...
Timeout error transaction.
Please wait. The next try to send this transaction is happening right now ...
Timeout error transaction.
Please wait. The next try to send this transaction is happening right now ...
Timeout error transaction.

But, it was sent successfully from one of the first attempts. I could see the successful tx in explorer, while near-cli was still saying "next try is happening right now". I just killed it after 8 repeats of timeout error.

Sorry for providing 2 issues in one, but it just gives you more context on what's going on. The second way worked for me, so there's a workaround which is good.

frol commented 7 months ago

First issue is resolved in the recent 0.8.0 release. Second issue is now resolved by Pagoda SRE team (there were issues with archival-rpc - ask Bohdan if you want to hear details)