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
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
Wait for future blocks in AuRa
The error is "PoW too low to compete with other messages" This has been previously reported in #7144 Solution: prevent the move semantics The source of the error is in PoolHandle.relay implementation for NetPoolHandle. Because of the move semantics, `res` variable is in fact copied (as it implements Copy) into the closure and for that reason, the returned result is always `false.
debris
added
A3-inprogress ⏳
Pull request is in progress. No review needed at this stage.
A8-backport 🕸
Pull request is already reviewed well in another branch.
labels
Jan 3, 2018
Strict config parsing
Firstly, `Step.duration_remaining` casts it to u32, unnecesarily limiting it to 2^32. While theoretically this is "good enough" (at 3 seconds steps it provides room for a little over 400 years), it is still a lossy way to calculate the remaining time until the next step. Secondly, step duration might be zero, triggering division by zero in `Step.calibrate` Solution: rework the code around the fact that duration is typically in single digits and never grows, hence, it can be represented by a much narrower range (u16) and this highlights the fact that multiplying u64 by u16 will only result in an overflow in even further future, at which point we should panic informatively (if anybody's still around) Similarly, panic when it is detected that incrementing the step counter wrapped around on the overflow of usize. As for the division by zero, prevent it by making zero an invalid value for step duration. This will make AuRa log the constraint mismatch and panic (after all, what purpose would zero step duration serve? it makes no sense within the definition of the protocol, as finality can only be achieved as per the specification if messages are received within the step duration, which would violate the speed of light and other physical laws in this case).
5chdn
added
the
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
label
Jan 3, 2018
5chdn
added
A0-pleasereview 🤓
Pull request needs code review.
and removed
A3-inprogress ⏳
Pull request is in progress. No review needed at this stage.
labels
Jan 3, 2018
We might want to hold on removing expanse for a second. Let's discuss this tomorrow. |
5chdn
added
the
A1-onice 🌨
Pull request is reviewed well, but should not yet be merged.
label
Jan 4, 2018
To be backported after review:
|
5chdn
removed
the
A1-onice 🌨
Pull request is reviewed well, but should not yet be merged.
label
Jan 5, 2018
…ivisor (#7463) * Byzantium Update for Expanse Here the changes go. Hope I didnt miss anything. * expip2 changes - update duration limit * Fix missing EXPIP-2 fields * Format numbers as hex * Fix compilation errors * Group expanse chain spec fields together * Set metropolisDifficultyIncrementDivisor for Expanse * Revert #7437 * Add Expanse block 900_000 hash checkpoint
* Advance AuRa step as far as we can. * Wait for future blocks.
Now only #7476 missing |
* Update Parity Mainnet Bootnodes * Replace the Azure HDD bootnodes with the new ones :)
@5chdn done |
Aaaand #7497 :) |
And maybe #7503 ? |
Use https when connecting to etherscan.io API for price-info
* Expose gas price percentile. * Fix light eth_call. * fix gas_price in light client
LGTM! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A0-pleasereview 🤓
Pull request needs code review.
A8-backport 🕸
Pull request is already reviewed well in another branch.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
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.
#7282 - d5b81ea
#7368 - f3e7d94
#7412 - 67a74e1
#7421 - 9c0fceb
#7433 - 51319eb
#7437 - 75f2921
#7476 - a553485
#7451 - 33b8f28
#7463 - 36e230e
#7495 - 7316cb9
#7497 - 69d7c4f
#7503 - ab7335d