- Mar 21, 2020
-
-
Shawn Tabrizi authored
Co-Authored-By: joe petrowski <[email protected]>
-
- Mar 20, 2020
-
-
Shawn Tabrizi authored
Co-Authored-By: Joseph Mark <[email protected]>
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
* Start benchmarks * try_origin or root * More benches * stuck * Custom trait functions for benchmarks * finish benchmarks * Bump impl * More comments * Bump spec * Remove import * Update frame/elections-phragmen/src/lib.rs Co-Authored-By: thiolliere <[email protected]> * Update frame/support/src/traits.rs Co-Authored-By: thiolliere <[email protected]> * Fix merge Co-authored-by: thiolliere <[email protected]>
-
Peter Goodspeed-Niklaus authored
* Factor out can_set_code The motivation for this feature is parachain runtime upgrades, which happen in two different moments: the initial call, when the checks should be performed, and at the actual upgrade block. It's much better and more maintainable to just call `can_set_code` in the function than to manually copy those checks. I'm not entirely thrilled with the interface, which requires cloning the entire code vector in `set_code`. However, it looks like something in `decl_module!` does not play nicely with references in its function arguments. If `code` has a lifetime, it _must_ be named, which gives us this signature. ```rust pub fn can_set_code<'a>(origin, code: &'a [u8]) { ``` Unfortunately, attempting to compile with that signature generates a very large and baffling collection of build errors, so I decided to abandon that path for now. * make can_set_code non-dispatchable per PR revew Not only can we now borrow the `code` slice, but we also no longer need to worry about people sending a `can_set_code` transaction because of some misunderstanding. * move into existing impl block
-
joe petrowski authored
-
Shawn Tabrizi authored
* Initial benchmarking setup * Add keystore * validate unsigned * Update frame/im-online/src/benchmarking.rs Co-Authored-By: Marcio Diaz <[email protected]> * Fix verify_unsigned benchmark * add variable for teting the external addresss length * Update frame/im-online/src/benchmarking.rs Co-Authored-By: Kian Paimani <[email protected]> * Update utils/frame/benchmarking-cli/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> Co-authored-by: Marcio Diaz <[email protected]> Co-authored-by: Kian Paimani <[email protected]> Co-authored-by: Benjamin Kampmann <[email protected]> Co-authored-by: Bastian Köcher <[email protected]>
-
- Mar 19, 2020
-
-
Gavin Wood authored
* Remove migration code. * Fix cargo * Bump spec version
-
lwshang authored
* Prompt error if vanity pattern is not valid base58 * Update bin/utils/subkey/src/vanity.rs * Add tests for validating pattern of subkey vanity Co-authored-by: Bastian Köcher <[email protected]>
-
Bastian Köcher authored
-
Benjamin Kampmann authored
* switching to released wasmtime * update depdencies in general * Update fdlimit * Update parity common deps * Also update schnorrkel * update kvdb-rocksdb * update further dependents * also update primitive types * update cargo.lock * update merlin * Bumping evm version
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Arkadiy Paronyan authored
* Don't queue duplicate blocks * Keep queue_blocks on restart
-
Shawn Tabrizi authored
-
Roman Borschel authored
env_logger::init() can lead to panics on concurrent test execution. See: https://gitlab.parity.io/parity/substrate/-/jobs/422283
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
André Silva authored
-
Shawn Tabrizi authored
-
André Silva authored
* grandpa: support for hard forking any pending standard changes * grandpa: expose authority_set_hard_forks in block import constructor * grandpa: don't break the public api
-
- Mar 18, 2020
-
-
Chevdor authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Max Inden authored
* client/network-gossip/src/bridge: Finish when network even stream closes Previously within `<GossipEngine as Future>::poll` one would poll the `network_event_stream` ignoring all messages other than `Poll::Ready(Some())`. Ignoring `Poll::Ready(None)` leads to a panic on the next poll of the stream, gien that it is not fused. By design `network_event_stream` does not close unless an unbounded send into it fails, or the `NetworkWorker` gets shut down. > The stream never ends (unless the `NetworkWorker` gets shut down). > (client/network/src/service.rs) An `unbounded_send` to fail on an unbounded channel is unlikely. The `NetworkWorker` shutting down is not unlikely. In such case the `GossipEngine` should shut down as well. With this patch a `<GossipEngine as Future>` finishes on `Poll::Ready(None)` returned from `network_event_stream`. * client/finality-grandpa/communication: Error on gossip engine finished Have `<NetworkBridge as Future>::poll` return `Poll::Ready(Err)` instead of `Poll::Ready(Ok)` to be consistent with the handling of the neighbor packet worker stream and the gossip validator report stream. Both `Err` as well as `Ok` shut down the `NetworkBridge` as well as the `VoterWorker`. * client/network-gossip/src/bridge: Add regression test * client/network-gossip: Move substrate test client to dev dependencies * client/network-gossip: Remove TODO Addressed in a follow up pull request. * client/network-gossip/bridge: Put match on newline after loop * client/finality-grandpa/src/observer: Fix regression test Make sure the event stream sender side is not dropped till the end.
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
-
Benjamin Kampmann authored
* Adding missing metadata for benchmark-pallet * Missed to bump a few * release on roling tag * Wasm executors were missed
-
Benjamin Kampmann authored
* Version bump * Split generate_changelog.sh into separate script Can be run in the format `generate_changelog.sh $previous_version $version`. * remove early exit from publish_draft_release.sh * adding changelog * ci: change last_github_release to also find pre-releases Co-authored-by: Martin Pugh <[email protected]>
-
ddorgan authored
-
Nikolay Volf authored
-
Toralf Wittner authored
If polling encounters a `Poll::Pending` we need to return it instead of continuing the loop which may turn it into a blocking operation, causing problems with executors.
-