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
{{ message }}
This repository has been archived by the owner on Jul 9, 2021. It is now read-only.
Basically as the title says. There's some ridiculous java-esque stack trace, here is the top:
TypeError: Cannot read property 'range' of null
at ASTVisitor._shouldIgnoreExpression (XXX-contract/node_modules/@0x/sol-tracing-utils/src/ast_visitor.ts:182:29)
at ASTVisitor._visitStatement (XXX-contract/node_modules/@0x/sol-tracing-utils/src/ast_visitor.ts:165:18)
at ASTVisitor.ExpressionStatement (XXX-contract/node_modules/@0x/sol-tracing-utils/src/ast_visitor.ts:92:14)
I was able to fix it by adding:
if (ast === null) return true;
to the top of the _shouldIgnoreExpression method in ast_visitor.ts.
Not sure if I have some weird solidity or something. It's possible, but I don't think I have anything that unusual.
After that change the report was generated OK and it looks pretty cool, so thanks!
The text was updated successfully, but these errors were encountered:
Thanks for reporting. Could you please attach the example contract where it happens? I'd like to know if it should be fixed on our side or on the AST parser side.
Basically as the title says. There's some ridiculous java-esque stack trace, here is the top:
I was able to fix it by adding:
to the top of the
_shouldIgnoreExpression
method inast_visitor.ts
.Not sure if I have some weird solidity or something. It's possible, but I don't think I have anything that unusual.
After that change the report was generated OK and it looks pretty cool, so thanks!
The text was updated successfully, but these errors were encountered: