Closed bout3fiddy closed 1 year ago
Weird thing to try, but can you try deleting your .build folder?
Oh okay, I believe this got fixed in ape-vyper and we need to release, I will ping when ready.
Weird thing to try, but can you try deleting your .build folder?
he did this privately and it did work
OK - I have not been able to reproduce but I tried so many things! I am deeply sorry!
The one thing I am pretty certain of is that the .build
folder was in a weird state from previous configuration / plugin versions, maybe even ethpm-types
version. IDK! So my solution is to raise an error directing to try removing the .build folder. Note, I really did try many version combinations, even installed vyper directly, and old versions of the contract itself... never got anything or the custom error to hit.... So if you have more detail there, I can try to make sure this actually does fix it. Otherwise, I think at least a better error when the revert will work (based on looking at the stacktrace here)
The one thing that stands out is that there is contract type name collision in that project - maybe somehow it was referencing the other one? shrug emoji
Finally was able to repro -- happens when using latest unreleased Vyper (follow #1398 which is same issue)
Environment information
ape
and plugin versions: 0.6.8ape-config.yaml
(NOTE: do not post anything private like RPC urls or secrets!):What went wrong?
running:
for the following contract:
https://github.com/curvefi/tricrypto-ng/blob/11cbaaa1c05b73763ea5c7cfe67b76fd4d247f1c/contracts/main/CurveCryptoMathOptimized3.vy
gives the following error:
How can it be fixed?
change: https://github.com/ApeWorX/ape/blob/c013bb82d58934b648093ac050e93d0fcee20c66/src/ape/managers/project/manager.py#L418
to:
and it magically works