Release - v1.0.0-beta.51

[nivida]

Description

Fixed issues:

#2587 #2560 #2542 #2595 #2591 #2553 #2583 #1021 #1517 #1074 #1169 #2033 #1793 #1126 #1134 #2578 #2569 #2563 #2571 #2570 #2565 #2558 #2559 #1802 #2551 #2554 #2555 #2539 #2532 #2350

Compare view beta.50 - beta.51

Type of change

• Release

Checklist:

• 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 warnings.
• I have updated or added types for all modules I've changed
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run test in the root folder with success and extended the tests if necessary.
• I ran npm run build in the root folder and tested it in the browser and with node.
• I ran npm run dtslint in the root folder and tested that all my types are correct
• I have tested my code on an ethereum test network.

[coveralls]

Coverage decreased (-0.04%) to 95.692% when pulling 67468b3 on release/1.0.0-beta.51 into 894c55c on 1.0.

[krychla1]

v1.0.0-beta.51 fixed the #2518->#2542, thank you, however new problem appeared.

sendSignedTransaction now throws timeout error (tx wasn't mined) despite it has been mined long before the timeout.
The exception object also contains valid receipt, confirmations, confirmationChecks, etc.

[mesirendon]

I just updated to beta 51 and it seems to have resolved the previous issue with the status (can't confirm though), but now I got another issue. It gets stuck getting the transaction receipt and getting the block by its number. I've attached a gif of my test.

It gets properly initialized, then trying to execute the first transaction is where it gets stuck.

I can provide more feedback of my code if needed.