-
Notifications
You must be signed in to change notification settings - Fork 145
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
JSException in XHR request #369
Comments
meditans
added a commit
to obsidiansystems/chainweaver
that referenced
this issue
Feb 7, 2022
This is because that version has been created to explicitly mask the errors on the js side, making them surface on the haskell side instead, see: reflex-frp/reflex-dom#369 While in this case the bug is not related to port numbers, I was wondering if the core mechanism of not letting exceptions show up is the same.
meditans
added a commit
to obsidiansystems/chainweaver
that referenced
this issue
Feb 7, 2022
This is because that version has been created to explicitly mask the errors on the js side, making them surface on the haskell side instead, see: reflex-frp/reflex-dom#369 While in this case the bug is not related to port numbers, I was wondering if the core mechanism of not letting exceptions show up is the same.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproducible example
ob run
Issue
Giving
xhrRequest
a url with a port number>= 2^16
makesnewXMLHttpRequestWithError
throw a JSException.with port 65535
![65535](https://user-images.githubusercontent.com/2335822/79054169-a10aac00-7c3a-11ea-8aa5-473dbbefbe52.png)
newXMLHttpRequestWithError
's callback is called...twice?...with different results?...maybe Fix xhr response handlers getting called 3 times. #255 ?with port 65536
![65536](https://user-images.githubusercontent.com/2335822/79053997-7f5cf500-7c39-11ea-834a-e0a63e61a914.png)
Total destruction - a JS exception is thrown, the callback isn't called, and the rest of the widget doesn't run. Commenting out the
newXMLHttpRequestWithError
makes things die later, whengetAndDecode
is run.The terminal console shows:
The text was updated successfully, but these errors were encountered: