-
Notifications
You must be signed in to change notification settings - Fork 109
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
Fix connection timeouts if server doesn't send something in time #525
Conversation
…n trying to set with ack the error callback was not triggered and the client hanged indefinitely.
There is still an issue with the emitter on L.562, is not being called properly when the record.set call is without callback (given the read and not write permission) |
Thank you, I’m currently offline (off tech offline) for a week so will get back to this then! |
@jaime-ez if you could write a basic client example that shows the issue I can fix it up. Unless it isn’t something easily reproducible, then let me know steps and I’ll put in a test to reproduce it that way (next week) |
No problem, it's simple to reproduce: On server set these permissions:
Then execute this on a file, expected behaviour described on code:
|
Amazing thank you, will look into this in a few days!i |
:100644 100644 29ae60b d2b44d6 M src/connection/socket-factory.ts
lgtm, would merge in except its blocked on
we could break that out into a separate issue and I can this merged and released, not sure if I'm going to be able to look into it right now due |
Ok for breaking it into a separate issue. Let me know if you need any help with it, last time I wasnt able to solve it. |
Will do thanks! |
Incredible thank you |
This prevents the client from hanging when a user tries to write to a record with ack but he only has read access.