- Oct 26, 2020
-
-
Peter Goodspeed-Niklaus authored
Co-authored-by: Bastian Köcher <[email protected]>
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
- Oct 25, 2020
-
-
Bastian Köcher authored
* Improve and unify testing facilities This improves the testing facilities by making the test client easier to use. It also removes code that is not required for the test client. Besides that it also moves the test service and test client under `node/test`. * Update Cargo.lock * Update node/test/client/src/block_builder.rs Co-authored-by: Andronik Ordian <[email protected]> * Remove explicit lifetime annotation * Fix warnings and add extra `BlockBuilderExt` Co-authored-by: Andronik Ordian <[email protected]>
-
- Oct 24, 2020
-
-
Fedor Sakharov authored
-
Sergey Pepyakin authored
* annoying whitespaces * update guide Add `CheckValidationOutputs` runtime api and also change the candidate-validation stuff * promote ValidationOutputs to global primitives i.e. move it from node specific primitives to global v1 primitives. This will be needed when we share it later in the runtime inclusion module * refactor acceptance checks in the inclusion module factor out the common code to share it during the block inclusion and for the forthcoming CheckValidationOutputs runtime api. Also note that the acceptance criteria was updated to incorporate checks that exist now in candidate-validation * plumb the runtime api outside * extract validation_data from ValidationOutputs * use runtime-api to check validation outputs apart from that refactor, update docs and tidy a bit * Update the maxium code size This is to fix a test that performs an upgrade.
-
Fedor Sakharov authored
* Initial commit * Move tests to separate module * Move timestamps to the newtype * Change idx name * Use Duration for consts and update chunk records * Ordering::Equal * Update node/core/av-store/src/lib.rs Co-authored-by: Peter Goodspeed-Niklaus <[email protected]> * put_ methods do the array sorting * Fix get_block_number * Change StoreChunk message type and relay parent method * Add chunk tests * Fix block number computation for StoreChunk * Duration instead of u64 everywhere * Add a clarifying comment Co-authored-by: Peter Goodspeed-Niklaus <[email protected]>
-
Robert Habermeier authored
-
- Oct 23, 2020
-
-
s3krit authored
-
Fedor Sakharov authored
-
Bernhard Schuster authored
-
Fedor Sakharov authored
-
Fedor Sakharov authored
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
Fedor Sakharov authored
-
- Oct 21, 2020
-
-
Bastian Köcher authored
-
Bastian Köcher authored
-
Cecile Tonglet authored
* WIP * WIP * WIP * WIP * WIP * WIP * Update node/service/src/lib.rs Co-authored-by: Bastian Köcher <[email protected]> * WIP * "Update Substrate" Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: parity-processbot <>
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
-
- Oct 20, 2020
-
-
s3krit authored
-
Peter Goodspeed-Niklaus authored
Prometheus lets us register simple counters, which aren't very interesting. It also allows us to register CounterVecs, which are. With a CounterVec, you can provide a set of labels, which can later be used to filter the counts. We were using them wrong, though. This pattern was repeated in a variety of places in the code: ```rust // panics with an cardinality mismatch let my_counter = register(CounterVec::new(opts, &["succeeded", "failed"])?, registry)?; my_counter.with_label_values(&["succeeded"]).inc() ``` The problem is that the labels provided in the constructor are not the set of legal values which can be annotated, but a set of individual label names which can have individual, arbitrary values. This commit fixes that.
-
Peter Goodspeed-Niklaus authored
detailed logging determined that using the `Box::new` style of future generation, the `self.run` method was never being called, leading to dropped receivers / closed senders for those subsystems, causing the overseer to shut down immediately. This is not the final fix needed to get things working properly, but it's a good start.
-
- Oct 19, 2020
-
-
s3krit authored
-
Peter Goodspeed-Niklaus authored
-
Peter Goodspeed-Niklaus authored
for debugging purposes, added this to node/subsystem-util/src/lib.rs:472-476: ```rust Some(registry) => Self::try_register(registry).map_err(|err| { eprintln!("PrometheusError calling {}::register: {:?}", std::any::type_name::<Self>(), err); err }), ``` That pointed out where the registration was failing, which led to this fix. The test still doesn't pass, but it now fails in a new and different way!
-
Bastian Köcher authored
* Companion for Substrate#7350 * "Update Substrate" Co-authored-by: parity-processbot <>
-
- Oct 17, 2020
-
-
Shawn Tabrizi authored
* Update constant weight signatures * Keep timestamp constant time * constant as_derivative * cargo update -p sp-io Co-authored-by: parity-processbot <>
-
- Oct 16, 2020
-
-
Bastian Köcher authored
* Make register/deregister parachain dispatchables This makes `register_parachain` and `deregister_parachain` of `Registrar` dispatchables. Besides that it brings back the functionality of the test node to register a parachain. * Fix tests * PR review comments
-
- Oct 15, 2020
-
-
André Silva authored
* runtime: remove finality-tracker * runtime: bump spec_version * update substrate
-
Peter Goodspeed-Niklaus authored
-
ordian authored
-
ordian authored
-
Peter Goodspeed-Niklaus authored
-
Ashley authored
* Add sync_state_items * Add SyncStateRpc * "Update Substrate" Co-authored-by: parity-processbot <>
-
- Oct 14, 2020
-
-
Sergey Pepyakin authored
-