-
Notifications
You must be signed in to change notification settings - Fork 391
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
Any request resulting in the error throws Uncaught exception #47
Comments
Also seeing this issue - changing the error -> restlererror does indeed fix the issue with the behaviour as amarchen describes. |
Looking at the LearnBoost thread, fix also looks quite simple, but it has to be done in the socket and I have no idea how to verify it. |
The above commit should fix this issue. |
Cool! Will probably give restler a try again next time I am on the same project again (currently just uses plain node.js and http for testing the remote API) |
I basically just implemented the same fix as in the link you sent. Fix is in v0.2.2. |
0.2.2? I didn't realize Restler has any versions at all. The project doesn't seem to have any branches, tags or downloads. Oh well, the fix is in the master branch anyway. |
there are versions on the npm registry. but you're right, restler should have tags for the versions. |
Any request resulting in the error code from the server side to client running node.js 0.6.0 and restler results in the following (or similar stack) trace:
Investigation showed that the problem is with the event name and is probably similar to (or same as) socketio/socket.io#476
For example changing
to
Makes everything work again, but of course event is incorrect then
The text was updated successfully, but these errors were encountered: