| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #1206
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
eth/downloader: handle timeouts more gracefully
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix two additional download vulnerabilities
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Start event has moved because it could possibly could stall the miner
|
|\
| |
| | |
eth/downloader: circumvent download race between crosscheck and hashes
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
eth, eth/downloader: handle a potential unknown parent attack
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
eth/downloader: fix deliveries to check for sync cancels
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Added a cancel method to the downloader which gracefully shuts down any
active syncing process (hash fetching or block downloading) and resets
the queue and remove any pending blocks.
Issue with the downloader which would stall because of an active ongoing
process when an invalid block was found.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If a peer fails to respond (disconnect, etc) during hash downloading
switch to a different peer which has it's current_hash in the queue's
peer set.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The downloader is no longer responsible for processing blocks. The
eth-protocol handler now takes care of this instead.
Added graceful shutdown during block processing. Closes #846
|
| |
|
|
|
|
| |
Peers in the eth protocol handler are now being ignored for catch up.
|
| |
|
| |
|
|
|
|
|
|
| |
When blocks have been sorted and are being processed, orphan blocks
should be ignored and thrown out. The protocol handler is responsible
for downloading blocks which have missing parents.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If all peers have been tried during the block download process and some
hashes are unfetchable (available peers > 0 and fetching == 0) throw an
error so the process can be aborted.
|
| |
|
| |
|
|
|
|
|
|
| |
* Downloader's peers keeps track of peer's previously requested hashes
so that we don't have to re-request
* Changed `AddBlock` to be fully synchronous
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
eth/downloader/downloader.go
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Properly ignore blocks coming from peers not in our peer list (blocked)
and do never request anything from bad peers. Added some checks to
account for blocks known when requesting hashes (missing parents).
|
|/
|
|
|
|
| |
Properly ignore blocks coming from peers not in our peer list (blocked)
and do never request anything from bad peers. Added some checks to
account for blocks known when requesting hashes (missing parents).
|
|
|
|
|
| |
When a parent is missing in the block list an attempt should be made to
fetch the missing parent and grandparents.
|
|
|
|
|
| |
If a peer was somehow already fetching and somehow managed to end up in
the `available` pool it should return it's work.
|
| |
|
|
|