-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add priority fee option/instruction for solana program deploy #34444
Comments
This is still an issue, anyone with context around the CLI would be most helpful if they could lend a hand on this? |
not an direct solution but i had issues with my deployments failing back when solana was on 1.9.x - 1.10.x and one workaround was to use https://beta.solpg.io/ to do deployments |
It's so frustrated to be unable to deploy an upgrade to my program after fixing the bugs. Please someone take a look at this. A simple config to set priority fees is enough for now. |
With the current network conditions, this is a must... |
I've been failing all my deploys... max retries for 5 times and 3~4 resumes for a couple of hours and still fails. I think priority fees could help with this |
Can something be done please ? It's starting to get ridiculous not being able to deploy for days |
I also face this issue. I am failing to deploy my program on chain continuously. someone can give me solution?? |
if anyone wants a quick solution, this was how i hardcoded priority fees for |
Added in anza-xyz#364 and present in 1.18.8, please upgrade to the latest tools |
Problem
Experiencing deployment failure caused by <1% of transactions failing every time. This has never happened so consistently before (have tried several RPC providers).
Proposed Solution
Add priority fees option to
solana program deploy
either microlamport or lamport amount to spend on entire deployment. Only issue is this means more transactions too since this new instruction will have ix data / account overhead.solana deploy program --buffer
seems to restart process rather than just resuming from previous deployment. If this is possible then this is preferred.Options to set max retry for failed buffer loading transactions. What good is failing the entire process if I can't resume from previous deployment attempt.
The text was updated successfully, but these errors were encountered: