- Jul 17, 2019
-
-
André Silva authored
-
- Jul 16, 2019
-
-
Demi M. Obenour authored
-
- Jul 15, 2019
-
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
The BABE code previously assumed `slots_per_epoch` to be a constant, but that assumption is false in general. Furthermore, removing this assumption also allows a lot of code to go away.
-
-
Sergey Pepyakin authored
-
Denis_P authored
* Logs will be saved to the job artifacts only in case of failure. * Logs will be partly shown at the end in case of failure. * expiration and parsing
-
- Jul 14, 2019
-
-
Pierre Krieger authored
* Remove block_imported * Move blocks results processing to sync * Remove methods from Link * Better errors * Allow cancelling the import queue * Restore the import trace * Fix network tests * Line widths * Use has_error instead * Minor style
-
- Jul 13, 2019
-
-
Demi M. Obenour authored
not a `Vec<AuthorityId>`.
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Pierre Krieger authored
* Switch the peerset to new futures * Fuse the peerset rx
-
Bastian Köcher authored
* Make parameter types implementation more flexible * Bump `impl_version`
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
The genesis block used by tests defines no authorities. Only the test suite is affected.
-
Demi M. Obenour authored
The BABE runtime was massively overcomplicated and also wrong. It assumed it needed to: 1. delay new authorities taking effect until the next epoch 2. not delay emitting `Consensus` digests to mark epoch changes However, the first is handled by the `srml_session` crate, and the second is flat-out incorrect: `Consensus` digests take effect immediately. Furthermore, `srml_babe` tried to duplicate the functionality of `srml_session::PeriodicSession`, but did it both clumsily and incorrectly. Fortunately, the new code is simpler and far more likely to be correct.
-
- Jul 12, 2019
-
-
Toralf Wittner authored
Instead of passing a context around to each method, thereby introducing side-effecting I/O actions everywhere, with this PR `sync::ChainSync` only contains state which is updated by invoking various callback methods (`on_*`) and actionable items are returned as regular results from method calls, often iterators yielding requests that should be issued to peers. It is up to the caller to handle these in an appropriate way, currently `protocol` will send those as messages.
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
- Jul 11, 2019
-
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-
Demi M. Obenour authored
It is not needed, and only served to waste space and cause confusion.
-
Demi M. Obenour authored
-
Demi M. Obenour authored
-