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

"The application panicked (crashed)." #969

Closed
AleksanderMisztal opened this issue Mar 9, 2023 · 4 comments
Closed

"The application panicked (crashed)." #969

AleksanderMisztal opened this issue Mar 9, 2023 · 4 comments

Comments

@AleksanderMisztal
Copy link

While running nargo prove I got

The application panicked (crashed).
Message: assertion failed: (left == right)
left: 1,
right: 0
Location: crates/noirc_frontend/src/hir_def/types.rs:114

This is a bug. Consider opening an issue at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.md

Reproduction here AleksanderMisztal/noir-experiments@9952b5e

@AleksanderMisztal
Copy link
Author

Another one:

The application panicked (crashed).
Message: no entry found for key
Location: crates/noirc_abi/src/input_parser/toml.rs:26

This is a bug. Consider opening an issue at https://github.com/noir-lang/noir/issues/new?labels=bug&template=bug_report.md

Reproduction: AleksanderMisztal/noir-experiments@f2178d5

@jfecher
Copy link
Contributor

jfecher commented Mar 9, 2023

Looking at the first examples real quick, I think the error is from this line:

impl DensePolynomial {

Which should be

impl<N> DensePolynomial<N> {

Since DensePolynomial is a generic type.

I'll work on verifying this is the actual error and adding a real error message for this if so, instead of crashing the compiler.

@TomAFrench
Copy link
Member

The second issue is due to you having an entry in your Prover.toml which doesn't exist in the ABI for your program. I'll add a better error message for this.

@TomAFrench
Copy link
Member

TomAFrench commented Mar 10, 2023

Closing this as we've added proper error types rather than panicking for these errors. Thanks for reporting these @AleksanderMisztal!

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

No branches or pull requests

3 participants