You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When deploying the contracts if the networks conditions change abruptly, an emitted tx can have a low gasPrice for being processed, and this situation can extend during long periods (particularly in polygon networks in my experience), and the deployment process is blocked until the pending tx go though (or you unblock that somehow externally).
This is the message shown:
Error: Timed out waiting for implementation contract deployment to address 0x7A6c6f0677c254f64dF748b3Ed31FadA46BB2D32 with transaction 0x3607c01c8b8d500e52b88bc5d0f679f706884e4066fcadbdef9b9eca526b08c8
Run the function again to continue waiting for the transaction confirmation. If the problem persists, adjust the polling parameters with the timeout and pollingInterval options.
Describe the solution you'd like
It would be nice if the deployment process could detect this situation and overwrite the tx with higher gasPrice for the current network conditions. Also a simple approach that I think could work would be overwriting a tx with oldGasPrice * 10 for the tx that is pending when continuing from cached deployment.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When deploying the contracts if the networks conditions change abruptly, an emitted tx can have a low gasPrice for being processed, and this situation can extend during long periods (particularly in polygon networks in my experience), and the deployment process is blocked until the pending tx go though (or you unblock that somehow externally).
This is the message shown:
Describe the solution you'd like
It would be nice if the deployment process could detect this situation and overwrite the tx with higher gasPrice for the current network conditions. Also a simple approach that I think could work would be overwriting a tx with oldGasPrice * 10 for the tx that is pending when continuing from cached deployment.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: