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

Backport "Don't updatePendingTxs outside of block updates (#8445)" #8474

Merged
merged 1 commit into from
Apr 30, 2020
Merged

Backport "Don't updatePendingTxs outside of block updates (#8445)" #8474

merged 1 commit into from
Apr 30, 2020

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Apr 30, 2020

Backport #8445 to v7.7.9. Original commit description:

  • Don't updatePendingTxs outside of block updates

Refs #8377

Reverts 507397f (#5431)

  • Check for new block data on unlock

@whymarrh @Gudahtt
Backport "Don't updatePendingTxs outside of block updates (#8445)"
3dedf89 
Backport #8445 to v7.7.9. Original commit description:

* Don't updatePendingTxs outside of block updates

Refs #8377

Reverts 507397f (#5431)

* Check for new block data on unlock
@Gudahtt Gudahtt mentioned this pull request Apr 30, 2020
Merged
@metamaskbot
Copy link
Collaborator

Builds ready [3dedf89]

@Gudahtt Gudahtt marked this pull request as ready for review April 30, 2020 13:24
@Gudahtt Gudahtt requested a review from a team April 30, 2020 13:24
@Gudahtt Gudahtt merged commit 14d4c10 into Version-v7.7.9 Apr 30, 2020
@Gudahtt Gudahtt deleted the backport-pending-tx-checks branch April 30, 2020 14:38
@metamaskbot metamaskbot mentioned this pull request May 1, 2020
Merged
@ryanml ryanml mentioned this pull request Jun 19, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@whymarrh whymarrh whymarrh approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Gudahtt @metamaskbot @whymarrh