Skip to content
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

Forward Buidler arguments #300

Merged
merged 3 commits into from
Jun 10, 2019
Merged

Forward Buidler arguments #300

merged 3 commits into from
Jun 10, 2019

Conversation

alcuadrado
Copy link
Member

Fixes #293

@alcuadrado alcuadrado merged commit f46abbd into master Jun 10, 2019
@alcuadrado alcuadrado deleted the forward-buidler-arguments branch June 10, 2019 20:57
@alcuadrado alcuadrado mentioned this pull request Jun 10, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 25, 2022
zoeyTM pushed a commit that referenced this pull request Dec 19, 2024
At the beginning of the execution run check run a check on the nonces of
any accounts going to be used in the deployment.

If there are pending user started transactions warn.
If there are Ignition transactions from a previous run continue

During batch processing check transactions for user interference or
dropping from the memory pool.

Resolves #300

feat: add check for pending ignition transactions

On initialization, check if the nonces match for in-flight transactions
from a previous run.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BuidlerArguments should be forwarded by the scripts-runner module
1 participant