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

handled "provider started to reconnect error" #5820

Merged
merged 3 commits into from
Feb 9, 2023

Conversation

avkos
Copy link
Contributor

@avkos avkos commented Feb 8, 2023

Description

Please include a summary of the changes and be sure to follow our Contribution Guidelines.

Fixes #4016 #3886
Origin PR

4.x was also tested - everything fine without any fixes

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist for 1.x:

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I ran npm run dtslint with success and extended the tests and types if necessary.
  • I ran npm run test:cov and my test cases cover all the lines and branches of the added code.
  • I ran npm run build with success.
  • I have tested the built dist/web3.min.js in a browser.
  • I have tested my code on the live network.
  • I have checked the Deploy Preview and it looks correct.
  • I have updated the CHANGELOG.md file in the root folder.

Checklist for 4.x:

  • I have selected the correct 4.x base branch.
  • Within the description, the feature or issue is discussed in detail or an issue is linked.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added any required tests for the changes I made
  • I have made corresponding changes to the documentation
  • Any dependent changes have been merged and published in downstream modules.
  • I ran yarn successfully
  • I ran yarn lint successfully
  • I ran yarn build:web successfully
  • I ran yarn test:unit successfully
  • I ran yarn test:integration successfully
  • I ran compile:contracts successfully
  • I have tested my code.
  • I have updated the corresponding CHANGELOG.md file in the packages I have edited.

@avkos avkos self-assigned this Feb 8, 2023
@avkos avkos requested a review from jdevcs February 8, 2023 01:01
@coveralls
Copy link

Pull Request Test Coverage Report for Build 4119726545

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 270 unchanged lines in 8 files lost coverage.
  • Overall coverage increased (+2.3%) to 75.021%

Files with Coverage Reduction New Missed Lines %
packages/web3-providers-ws/lib/index.js 1 93.16%
packages/web3-core-requestmanager/src/jsonrpc.js 2 64.29%
packages/web3-core-helpers/src/formatters.js 8 84.3%
packages/web3-core-helpers/src/errors.js 29 1.56%
packages/web3-utils/src/soliditySha3.js 34 3.43%
packages/web3-utils/src/index.js 40 40.3%
packages/web3-utils/src/utils.js 45 10.67%
packages/web3-eth-accounts/src/index.js 111 22.94%
Totals Coverage Status
Change from base Build 4058099322: 2.3%
Covered Lines: 3300
Relevant Lines: 4148

💛 - Coveralls

@avkos avkos changed the title fix handled "provider started to reconnect error" Feb 8, 2023
Copy link
Contributor

@jdevcs jdevcs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

update in changelog is also required.

@avkos avkos merged commit 8621030 into 1.x Feb 9, 2023
@avkos avkos deleted the ok/handled-provider-started-to-reconnect-error- branch February 9, 2023 15:29
@jdevcs jdevcs mentioned this pull request Mar 7, 2023
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

Successfully merging this pull request may close these issues.

One particular block cannot be read over websocket: "CONNECTION ERROR: Provider started to reconnect"
4 participants