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 provider reconnecting timeout and reconnection event added #2994

Merged
merged 4 commits into from
Aug 2, 2019
Merged

Websocket provider reconnecting timeout and reconnection event added #2994

merged 4 commits into from
Aug 2, 2019

Conversation

nivida
Copy link
Contributor

@nivida nivida commented Aug 2, 2019

No description provided.

@nivida nivida added Enhancement Includes improvements or optimizations In Progress Currently being worked on 2.x 2.0 related issues labels Aug 2, 2019
@nivida nivida changed the title Websocket provider reconnecting timeout and reconnected event added Websocket provider reconnecting timeout and reconnection event added Aug 2, 2019
@coveralls
Copy link

coveralls commented Aug 2, 2019 •
edited
Loading

Coverage Status

Coverage increased (+0.01%) to 95.335% when pulling 11bcdda on feature/websocket-provider-reconnecting-timeout into 704e7a3 on 2.x.

@nivida nivida removed the In Progress Currently being worked on label Aug 2, 2019
@nivida nivida merged commit b92926c into 2.x Aug 2, 2019
@nivida nivida deleted the feature/websocket-provider-reconnecting-timeout branch August 4, 2019 20:18
@nivida nivida mentioned this pull request Aug 5, 2019
Merged
11 tasks
@alcuadrado alcuadrado mentioned this pull request Sep 16, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
2.x 2.0 related issues Enhancement Includes improvements or optimizations
Projects
No open projects
1.0 Stable
Awaiting triage
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@nivida @coveralls