Do not run KZG compute challenge tests in the collection phase#4546
Merged
jtraglia merged 1 commit intoethereum:masterfrom Aug 28, 2025
Merged
Do not run KZG compute challenge tests in the collection phase#4546jtraglia merged 1 commit intoethereum:masterfrom
jtraglia merged 1 commit intoethereum:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The alpha.6 release stalled in the reference test generation step because of this. When adding these, I forgot to use an input getter function, so it was computing the blob's commitment in the test collection phase. For some reason, this caused latest usage of
arkworks_G1.multiexp_uncheckedto completely halt. I think it has something to do with mixing up Rust'srayonand Python's threading here.