- Mar 23, 2020
-
-
Max Inden authored
The Prometheus Rust crate offers process related metrics with the `process` feature. This patch enables the feature on non-wasm platforms and registers the process metrics with the Substrate registry. In addition it removes the existing manually exposed cpu and memory metrics. The first block of metrics is replaced by the second block of metrics. ``` \# HELP substrate_cpu_usage_percentage Node CPU usage \# TYPE substrate_cpu_usage_percentage gauge substrate_cpu_usage_percentage 1.2066365480422974 \ # HELP substrate_memory_usage_bytes Node memory usage \ # TYPE substrate_memory_usage_bytes gauge substrate_memory_usage_bytes 86628 ``` ``` \# HELP substrate_process_cpu_seconds_total Total user and system CPU time spent in seconds. \# TYPE substrate_process_cpu_seconds_total counter substrate_process_cpu_seconds_total 1.05 \# HELP substrate_process_max_fds Maximum number of open file descriptors. \# TYPE substrate_process_max_fds gauge substrate_process_max_fds 1048576 \# HELP substrate_process_open_fds Number of open file descriptors. \# TYPE substrate_process_open_fds gauge substrate_process_open_fds 99 \# HELP substrate_process_resident_memory_bytes Resident memory size in bytes. \# TYPE substrate_process_resident_memory_bytes gauge substrate_process_resident_memory_bytes 104386560 \# HELP substrate_process_start_time_seconds Start time of the process since unix epoch in seconds. \# TYPE substrate_process_start_time_seconds gauge substrate_process_start_time_seconds 1584963169.7 \# HELP substrate_process_virtual_memory_bytes Virtual memory size in bytes. \# TYPE substrate_process_virtual_memory_bytes gauge substrate_process_virtual_memory_bytes 2903089152 ```
-
- Mar 22, 2020
-
-
ordian authored
-
- Mar 21, 2020
-
-
Stanislav Tkach authored
-
ddorgan authored
-
Gavin Wood authored
* Repot a bit of democracy code * Basic logic is drafted * Lazy democracy builds. * Add non-locked split-voting and instant-scheduling. * Introduce delegation that works. * Builds again. * Indentation * Building. * Docs and migration * Fix half of the tests * Fix up & repot tests * Fix runtime build * Update docs * Docs * Nits. * Turnout counts full capital * Delegations could towards capital * proxy delegation & proxy unvoting * Fix * Tests for split-voting * Add missing file * Persistent locking.
-
joe petrowski authored
* minor fixes to CLI arg docs * Update client/cli/src/params/shared_params.rs Co-authored-by: Bastian Köcher <[email protected]>
-
- Mar 20, 2020
-
-
Benjamin Kampmann authored
-
Bastian Köcher authored
* Adds new event phase `Initialization` Every event that was deposited inside of `on_initialize` was assigned to the `ApplyExtrinsic(0)` phase which wasn't correct. This pr introduces a new phase `Initialization`. This is the new phase while initializing a block. After initialization we switch to `ApplyExtrinsic(N)` and at the end to `Finalization` as before. * Set `ExecutionPhase` in `initialize` * Increment `spec_version`
-
André Silva authored
* grandpa: allow noting same set in gossip with different authorities * grandpa: add test for note_set behavior
-
Bastian Köcher authored
-
Hero Bird authored
* Implement ext_ hashes for contracts (issue #5258) * load cryto hash .wat from raw string literal instead of file * update .wat contents for testing crypto hashes * remove unnecessary 'static * fix bug in input (call_indirect required 1+ at least it seems) * no longer use scratch buffer for crypto hash functions * improve doc comments of ext_ hash functions * remove unnecessary comment in .wat test file * add return value (const 0) to contract test to hopefully enable result buffer * fix bug in contract assertion * implement proper output_len in contract * implement proper test for crypto hashes * bump spec_version 238 -> 239 * fix COMPLEXITY description * remove final invalid instances of scratch buffer from docs
-
Bastian Köcher authored
* Make sure frame examples compile for wasm This makes sure that `frame-example` and `frame-example-offchain-worker` compile for wasm. This also fixes compilation for these crates. The offchain worker example doesn't use serde-json anymore as that is too heavy and breaks `no_std` compilation. * Apply suggestions from code review Co-Authored-By: Nikolay Volf <[email protected]> Co-authored-by: Nikolay Volf <[email protected]>
-
Pierre Krieger authored
* Remove the #[doc(hidden)] reexports of sc_network * Fix tests not building
-
Benjamin Kampmann 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
-
Arkadiy Paronyan authored
* Don't queue duplicate blocks * Keep queue_blocks on restart
-
Roman Borschel authored
env_logger::init() can lead to panics on concurrent test execution. See: https://gitlab.parity.io/parity/substrate/-/jobs/422283
-
André Silva 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
-
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.
-
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.
-
gabriel klawitter authored
-
lwshang authored
* Print non-output messages to stderr in subkey * Update bin/utils/subkey/src/main.rs Co-authored-by: Bastian Köcher <[email protected]>
-
derfredy authored
-
- Mar 17, 2020
-
-
nahuseyoum authored
if statement logic for recently sent block was inverted.
-
Nikolay Volf authored
* make sure return ready iterator once state is updated * update sc_basic_authorship tests * update node tests * fix manual seal * actually fix service test * add tests * Update client/basic-authorship/src/basic_authorship.rs Co-Authored-By: Tomasz Drwięga <[email protected]> * helper function * review suggestions * warning and continue * add debug log * use futures::chennel::oneshot * use declaration bound * no option for updated_at * no allocation * ready_at / ready * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> * Update client/transaction-pool/src/lib.rs Co-Authored-By: Bastian Köcher <[email protected]> Co-authored-by: Tomasz Drwięga <[email protected]> Co-authored-by: Bastian Köcher <[email protected]>
-
Marcio Diaz authored
* Fix vesting bench starting block. * Set subs s+1 to hit worst path. * Remove unused origin. * Apply review suggestions.
-