-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solana 1.18.8 hangs when deploying #1018
Comments
Same with 1.18.11, even with high |
Same issue here, and have also seen other people encountering it. |
Same issue, across multiple versions and architectures. Don't know how to get past it.. |
I had to fork the 1.14.29 version and made a change to the number of retry attempts. It finally worked after about 30 retries... |
Can confirm this works. Forked and changed the retry amount and it's not hanging. Thanks! https://github.com/solana-labs/solana/blob/v1.14.29/client/src/tpu_client.rs#L224 |
It works. Thanks, you saved my life <3 |
Even 30 retries didn't help. Seems, I should add prioritization fee to the old cli. |
Same issue #35534 |
Making a fork, adding a timeout to Athough it's really slow but did the job eventually (40 retries over 1.5 hours) |
Working for me now with --use-rpc flag and helius + jito + ironforge RPC on 1.18.12 |
CLI: 1.18.12 Verified it wasn't a swallowing of 429s by running Error: HTTP status client error (429 Too Many Requests) for url XXXX Found that hanging doesn't actually happen, but time between |
Problem
When running
solana program deploy
with solana v1.18.8, the process will hang indefinitely and not resign/resend transactions after a while. There's no 5 retries like previous versions.This causes the buffer account's seed phrase to never be printed, therefore the only option left is to close the buffer account through
solana program close
.Proposed Solution
It should throw an error together with the seed phrase of the buffer account like it did before, so we know when to restart/resume the deploy.
The text was updated successfully, but these errors were encountered: