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
Parser stalls indefinitely for certain input files #9571
Comments
@rwcarlsen - will your parser handle this case? |
For full backward compatibility it should go into an infinite loop, too. |
Moose (c++) parser or the python one? Also, does it loop forever in other blocks (not just |
The old C++ parser is the one that locks up. The new parser will have a common C++/python (cython) code base, right? It does not lock up if the block closing tag is on a separate line. |
New parser (mostly) doesn't care about whitespace. You will soon be able to have one-line input files! We haven't fully decided if we prefer python bindings to the new c++ parser or just to have a separate but similarly architected new python parser (which I have already written) with a shared set of tests between the two. |
Will we have an Obfuscated MOOSE Contest as well? |
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
…rror messages fixes idaholab#9571
Description of the enhancement or error report
Open and closing tags in variable blocks (possibly elsewhere, too) cause the parser to stall (possibly run into an infinite loop).
Rationale for the enhancement or information for reproducing the error
Minimal input to reproduce the bug:
Identified impact
Bad behavior. Malformed input should not cause the code to stall indefinitely.
The text was updated successfully, but these errors were encountered: