Skip to content
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

Submission to suggest a fix for issue : Add on-the-fly proof generation #26 #30

Merged
merged 11 commits into from
Jun 15, 2023

Conversation

bbresearcher
Copy link
Contributor

Description

Problem*

Submission to try help with a fix for issue : Add on-the-fly proof generation #26

Resolves

Summary*

Added dynamic test code to Starter.t.sol in test directory.

Additional Context

PR Checklist*

  • [ x] I have tested the changes locally.
  • I have formatted the changes with Prettier and/or cargo fmt on default settings.

@netlify
Copy link

netlify bot commented Jun 14, 2023

‼️ Deploy request for noir-next-hardhat rejected.

Name Link
🔨 Latest commit a8fec9f

@signorecello
Copy link
Collaborator

signorecello commented Jun 14, 2023

Thanks for your contribution @bbresearcher.

Could you please just fix this CI? Seems like it wants the -ffi flag

Apologies, adding ffi in the foundry.toml so it's not needed to be added to the forge test command
@bbresearcher
Copy link
Contributor Author

Apologies for that, I have made changes to add ffi permissions by default in the foundry.toml file.

@critesjosh
Copy link
Collaborator

@bbresearcher Have you tested this in with multiple tests?

@signorecello tried this earlier and there are some irresolvable race conditions (iirc) with writing to the Prover.toml with multiple tests. this can be resolved by running 1 test at a time I believe, you just might want to add that to the README.

@bbresearcher
Copy link
Contributor Author

@critesjosh and @signorecello : I am trying to see if I can come up with a solution, my tests fail with 3 or 4 dynamic proof generations, I will test a few ways and then let you know if I was able to solve it, or if I am just going to add instructions in the README.

@bbresearcher
Copy link
Contributor Author

Hi @critesjosh and @signorecello I have managed to find a way to resolve the race condition, please may I ask if you could verify that? I have cloned a clean version and followed the readme and it worked, I made sure my /tmp was cleaned of old artefacts as well.

@critesjosh
Copy link
Collaborator

Awesome! 🙌 I am on my phone but will test when I'm at my computer.

Just curious where you found the solution, do you have a link?

@bbresearcher
Copy link
Contributor Author

bbresearcher commented Jun 15, 2023

@critesjosh I must be honest I came up with it by myself, I did not google anything. the initial idea was based on the tweet you linked and also how I deployed a vyper contract before in foundry but the race fix was just an idea

@critesjosh
Copy link
Collaborator

Ah even better!

@critesjosh critesjosh merged commit 7b1d94a into AztecProtocol:main Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants