-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Specify node version that this repo works with #1
Comments
Weird... |
@vdg0 what kind of errors are you getting? |
I don't remember specifics anymore and don't catch that log. |
Hi @andreiashu! Thanks for the suggestion, it is really appreciated. The project owner will review your suggestion as soon as they can. Please wait until we have discussed this idea before writing any code or submitting a Pull Request, so we can go through the design beforehand. We don’t want you to waste your time! |
Thanks @andreiashu for reporting! I'll take a closer look during the weekend, I never had a problems with node's version during testing, but it might be the case some dependencies don't work with specific versions. I'll come back here once I have it clearer. |
I have been able to install all dependencies and run all challenges with version Thanks for reporting @andreiashu and @vdg0 |
Attacker transfers tokens to pool causing pool's tracking of pool balance to be out of sync with actual pool balance. Pool's ability to execute flash loans is halted because an equality assertion is made between queried value of pool balance before loan and tracked valued of pool balance within contract.
* Partial work on v2 * Add Free Rider challenge * Change package scripts * Add Puppet v2 * Ease wording * Limit ETH in climber * Further cleanup before release
Running the tests in node v14 throws errors in before/after hooks:
Error: Callback was already called.
Might be worth:
Let me know your thoughts. I can send a PR but just wanted to get your thoughts first.
PS: thanks for this great work
Edit: forgot to mention, but everything works as expected with
v12.11.1
The text was updated successfully, but these errors were encountered: