This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
parity: fix db path when migrating to blooms db #8975
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
No F-labels on PRs please 😆 |
I need to print that and hang it on my wall. 🙈 |
CI failure seems legit? |
758992d
to
9f2d91e
Compare
Should be fixed now. |
CI failure seems unrelated now:
|
@andresilva seems like the same CI issue I'm seeing on #8973 (which is why I went checking other PRs CI status yesterday!) |
debris
approved these changes
Jun 26, 2018
please rebase on latest master |
9f2d91e
to
c186ec6
Compare
niklasad1
approved these changes
Jun 28, 2018
ordian
added a commit
to ordian/parity
that referenced
this pull request
Jul 9, 2018
…rp_sync_on_light_client * 'master' of https://github.com/paritytech/parity: parity: fix db path when migrating to blooms db (openethereum#8975) Preserve the current abort behavior (openethereum#8995) Improve should_replace on NonceAndGasPrice (openethereum#8980) Tentative fix for missing dependency error (openethereum#8973)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.