We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Test if malformed input is handled correctly
Assertion failure (the test should have failed
Json parser ignores ""}" in the end
#[test(should_fail)] fn closing_bracket() { let json_string = "{ } \"}"; let json_string_bytes = json_string.as_bytes(); let mut json_buffer = [32; 512]; for i in 0..json_string_bytes.len() { json_buffer[512 - json_string_bytes.len() + i] = json_string_bytes[i]; } let json = JSON512b::parse_json(json_buffer); }
None
No response
nargo version = 1.0.0-beta.1 noirc version = 1.0.0-beta.1+6d85cd6d52eebdaa7a91a019dddf21df4351f707
The text was updated successfully, but these errors were encountered:
There is a similar issue. I don't know it it's separate or the same:
#[test(should_fail)] fn forward_slash() { let json_string = "{}\"\t/}"; let json_string_bytes = json_string.as_bytes(); let mut json_buffer = [32; 512]; for i in 0..json_string_bytes.len() { json_buffer[512 - json_string_bytes.len() + i] = json_string_bytes[i]; } let json = JSON512b::parse_json(json_buffer); }
Sorry, something went wrong.
kashbrti
No branches or pull requests
Aim
Test if malformed input is handled correctly
Expected Behavior
Assertion failure (the test should have failed
Bug
Json parser ignores ""}" in the end
To Reproduce
Workaround
None
Workaround Description
No response
Additional Context
No response
Project Impact
None
Blocker Context
No response
Nargo Version
nargo version = 1.0.0-beta.1 noirc version = 1.0.0-beta.1+6d85cd6d52eebdaa7a91a019dddf21df4351f707
NoirJS Version
No response
Proving Backend Tooling & Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: