-
Notifications
You must be signed in to change notification settings - Fork 53
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
(Need help) AST parser fails due to missing "ast" field #191
Comments
@alexroan It appears to me that the new format of json files output by solc doesn't contain ast node example : Error reading Foundry output file: /XXX/tests/contract-playground/out/Counter.sol/Counter.json: missing field `ast` at line 1 column 7588
Error reading Foundry output file: /XXX/tests/contract-playground/out/2/Nested.sol/Nested.json: missing field `ast` at line 1 column 4285 I am finding it difficult to reproduce json output Do you mind taking a look at it ? |
You're right, output files don't actually produce an AST object in the json after running foundryup |
foundry-rs/foundry#7197 <- Here's the culprit I've added this PR to fix this issue: #192 |
Thanks Alex, for showing me where it originated! |
Sorry about that folks - we should have notified users! |
Helloi @gakonst ! It's okay ... It's been fixed now : ) I have a small question for you. Would greatly appreciate any thoughts. So right now, we're shelling out I was wondering if it's possible that we can use forge codebase as a rust dependency somehow in the Cargo.toml file and make this operation happen ... What do you think ? Good idea / bad idea / doesn't matter....haha which one is it.:P ?? |
I like where your head is at. Perhaps open an issue/PR in the foundry codebase @TilakMaddy ? |
Step 1. Nuke the
~/.svm
folder (where foundry installs solc)Step 2. foundryup
Step 3. forge build
Then AST parser fails
Sample of the output of
cli/reportgen.sh
Any help is greatly appreciated : )
I am concerned that for nyth projects, in the testing section we pass the path to json file. Can this be something we can avoid ?
The text was updated successfully, but these errors were encountered: