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.

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

Provider does not reconnect after failure #1085

Closed
gabi-t opened this issue Sep 28, 2017 · 1 comment
Closed

Provider does not reconnect after failure #1085

gabi-t opened this issue Sep 28, 2017 · 1 comment
Assignees

Comments

@gabi-t
Copy link

gabi-t commented Sep 28, 2017

How to reproduce:

  1. instantiate a web3 instance using a websockets provider (in my case - I connected it to a local parity client)
  2. create a subscription to an event (in my case - newBlockHeaders)
  3. kill parity
    Result: The process crashes with the following output:
    [..]node_modules/web3-core-subscriptions/src/subscription.js:279
    _this.options.requestManager.provider.reconnect();
    ^
    TypeError: _this.options.requestManager.provider.reconnect is not a function
    at Timeout._onTimeout ([..]node_modules/web3-core-subscriptions/src/subscription.js:279:67)
    at ontimeout (timers.js:488:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:283:5)
@nivida
Copy link
Contributor

nivida commented Mar 25, 2019

This got implemented with version beta.38

@nivida nivida closed this as completed Mar 25, 2019
@nivida nivida removed the In Progress Currently being worked on label Mar 25, 2019
@nivida nivida mentioned this issue Nov 21, 2019
7 tasks
@ryanio ryanio mentioned this issue Apr 15, 2020
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants