-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
JSON parse error in wasm version causes very long system error to be printed #533
Comments
Thank you for reporting this. I can not reproduce this in Firefox. I copied the And no JavaScript errors are appearing. I also tested it in the CLI version and everything works as expected. Interestingly though, I experienced a potentially related error today. I did something like this … … in a slightly different environment, and only saw numbat/numbat/src/html_formatter.rs Line 72 in 2ead484
which needs to call Maybe something similar happened in your case?! Or it is something else entirely. But then I need some help with reproducing this. The escaping problem should definitely be fixed though. |
@Mads-MMJ any feedback on this? |
I'm closing this due to inactivity. Please feel free to comment in case it should be re-opened. |
Description
I was playing around with making a generic numbat function for creating list representations of mixed units after reading #364 and #501. When I tried to test it on the
Angle
Dimension I tried to use the minute and second symbols but used the wrong characters by accident. This however caused a parsing error which took several seconds (roughly 10) to print while read text filled the screen.It looks a lot like an unhandled exception that rose all the way to the user by accident. For the sake of reproducibility, I have included the error and my implementation of the function that caused it. I can however not include the full error due to the GitHub character limit. I do however have the full error and full session history saved and can provide it if needed.
Error
Implementation of unit_list
The text was updated successfully, but these errors were encountered: