Skip to content
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.

Sign up for GitHub

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

Jump to bottom

websocket.setdefaulttimeout() affects other WebSocket clients #413

Closed
FeodorFitsner opened this issue Sep 29, 2022 · 0 comments
Closed

websocket.setdefaulttimeout() affects other WebSocket clients #413

FeodorFitsner opened this issue Sep 29, 2022 · 0 comments
Labels
bug Something isn't working
Milestone
Controls-S2

Comments

@FeodorFitsner
Copy link
Contributor

No description provided.

@FeodorFitsner FeodorFitsner added the bug Something isn't working label Sep 29, 2022
@FeodorFitsner FeodorFitsner changed the title websocket.setdefaulttimeout(5) affects other WebSocket clients websocket.setdefaulttimeout() affects other WebSocket clients Sep 29, 2022
@FeodorFitsner FeodorFitsner added the status: working on it Working on a fix for the issue label Oct 2, 2022
@FeodorFitsner FeodorFitsner added this to the Controls-S2 milestone Oct 5, 2022
@FeodorFitsner FeodorFitsner removed the status: working on it Working on a fix for the issue label Oct 5, 2022
FeodorFitsner added a commit that referenced this issue Oct 6, 2022
@FeodorFitsner
Restore websocket.defaulttimeout on connect
3d72689 
Fix #413
@FeodorFitsner FeodorFitsner added the status: working on it Working on a fix for the issue label Oct 6, 2022
@FeodorFitsner FeodorFitsner removed the status: working on it Working on a fix for the issue label Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Controls-S2
Development

No branches or pull requests
1 participant
@FeodorFitsner