You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have weird users submitting weird strings - and one of them triggered a fatal error for "Maximum function nesting level of X reached, aborting!"
There isn't a way to catch and handle the error or detect it before starting to parse so I'm hoping Parsedown could have a fail-safe in that case that'll allow us to choose how to handle these cases.
The string is: _________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________.EXE
I suggest tracking the depth when parsing inner elements and being able to specify a limit before parsing. Optionally, just before the limit is reached it could use another option to tell it what to do: either throw an exception or attach the raw, unparsed inner element.
By the way, really appreciate your work on this lib! We've been using it for quite a while now and it's been mostly good to us :)
The text was updated successfully, but these errors were encountered:
Heya!
We have weird users submitting weird strings - and one of them triggered a fatal error for "Maximum function nesting level of X reached, aborting!"
There isn't a way to catch and handle the error or detect it before starting to parse so I'm hoping Parsedown could have a fail-safe in that case that'll allow us to choose how to handle these cases.
The string is:
_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________.EXE
I suggest tracking the depth when parsing inner elements and being able to specify a limit before parsing. Optionally, just before the limit is reached it could use another option to tell it what to do: either throw an exception or attach the raw, unparsed inner element.
By the way, really appreciate your work on this lib! We've been using it for quite a while now and it's been mostly good to us :)
The text was updated successfully, but these errors were encountered: