Essentially, this problem boils down to the fact that parse_type has a bug. I debugged it for a little while, but then realised that there is an easier way to solve the problem. There is no need to go from canonical type string back to Python representation. There is an ABIType that can be easily utilised to produce what parse_type was producing, but bug free.
Environment information
ape
and plugin versions:ape
: 0.5.3. But I could reproduce the same issue in 0.5.4But this bug has nothing to do with plugins
ape-config.yaml
(NOTE: do not post anything private like RPC urls or secrets!):This also doesn't matter.
What went wrong?
And discord link to the above.
Essentially, this problem boils down to the fact that
parse_type
has a bug. I debugged it for a little while, but then realised that there is an easier way to solve the problem. There is no need to go fromcanonical
type string back to Python representation. There is anABIType
that can be easily utilised to produce whatparse_type
was producing, but bug free.How can it be fixed?
Going to link the fix here shortly.