-
Notifications
You must be signed in to change notification settings - Fork 44
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
Bug causing parser error in front which needs looking at #49
Comments
this this is in the back end. With the new logging now seeing this in the front end: Error parsererror SyntaxError: Unexpected end of input |
This is subtle and has taken a lot of tracking down as there's not an exception in sight... It appears to be caused because the backend sends the HTTP success headers before calculating the response. If the response calculation takes too long, then the web browser assumes the response is complete, and passes the still empty response body to the javascript. |
…r flow control which could have caused exceptions being wrongly swallowed
Fix for #49 and removed more exception handling being used for flow control
Looks fixed now. |
when doing certain domains with all the generation options on seeing a couple of errors which I had to handle a fail condition for to allow the front end UI to complete. Need to investigate when I get time.
The text was updated successfully, but these errors were encountered: