1. 05 Dec, 2022 1 commit
    • Dmitry Markin's avatar
      Upgrade tokio to 1.22.0 and replace async-std with tokio (#12646) · 2bde8c1a
      Dmitry Markin authored
      * Replace deprecated libp2p feature specs with correct ones
      * Bump tokio to 1.21.2
      * Replace async-std libp2p primitives with tokio ones
      * minor: rustfmt
      * Fix TestNet to run initialization in the tokio context
      * Convert telemetry test from async-std to tokio
      * Convert notifications tests from async-std to tokio
      * Convert chain sync tests from async-std to tokio
      * Ditch async-std completely
      * Make executor mandatory
      * Bump tokio to 1.22.0
      * minor: rustfmt
      * Explicitly use tokio runtime in tests
      * Move more tests to explicit tokio runtime
      * Explicitly set multithreaded runtime in tokio test
      * minor: rustfmt
      * minor: fix comment
      * Replace async-std with tokio in MMR tests
  2. 11 Apr, 2022 1 commit
    • Koute's avatar
      Add new hardware and software metrics (#11062) · 5597a93a
      Koute authored
      * Add new hardware and software metrics
      * Move sysinfo tests into `mod tests`
      * Correct a typo in a comment
      * Remove unnecessary `nix` dependency
      * Fix the version tests
      * Add a `--disable-hardware-benchmarks` CLI argument
      * Disable hardware benchmarks in the integration tests
      * Remove unused import
      * Fix benchmarks compilation
      * Move code to a new `sc-sysinfo` crate
      * Correct `impl_version` comment
      * Move `--disable-hardware-benchmarks` to the chain-specific bin crate
      * Move printing out of hardware bench results to `sc-sysinfo`
      * Move hardware benchmarks to a separate messages; trigger them manually
      * Rename some of the fields in the `HwBench` struct
      * Revert changes to the telemetry crate; manually send hwbench messages
      * Move sysinfo logs into the sysinfo crate
      * Move the `TARGET_OS_*` constants into the sysinfo crate
      * Minor cleanups
      * Move the `HwBench` struct to the sysinfo crate
      * Derive `Clone` for `HwBench`
      * Fix broken telemetry connection notification stream
      * Prevent the telemetry connection notifiers from leaking if they're disconnected
      * Turn the telemetry notification failure log into a debug log
      * Rename `--disable-hardware-benchmarks` to `--no-hardware-benchmarks`
  3. 03 Apr, 2022 1 commit
  4. 03 Jan, 2022 1 commit
  5. 21 Jul, 2021 1 commit
    • Bastian Köcher's avatar
      Run cargo fmt on the whole code base (#9394) · 1d5abf01
      Bastian Köcher authored
      * Run cargo fmt on the whole code base
      * Second run
      * Add CI check
      * Fix compilation
      * More unnecessary braces
      * Handle weights
      * Use --all
      * Use correct attributes...
      * Fix UI tests
      * 🤦
      * Docs
      * Fix compilation
      * 🤷
      * Please stop
      * 🤦
       x 2
      * More
      * make rustfmt.toml consistent with polkadot
      Co-authored-by: default avatarAndré Silva <andrerfosilva@gmail.com>
  6. 17 Feb, 2021 1 commit
    • Cecile Tonglet's avatar
      Fix telemetry span not entering properly attempt 3 (#8043) · 743accbe
      Cecile Tonglet authored
      * Fix tracing tests (#8022)
      * Fix tracing tests
      The tests were not working properly.
      1. Some test was setting a global subscriber, this could lead to racy
      conditions with other tests.
      2. A logging test called `process::exit` which is completly wrong.
      * Update client/tracing/src/lib.rs
      Co-authored-by: David's avatarDavid <dvdplm@gmail.com>
      * Review comments
      Co-authored-by: David's avatarDavid <dvdplm@gmail.com>
      * Fix tracing spans are not being forwarded to spawned task (#8009)
      * Fix tracing spans are not being forwarded to spawned task
      There is a bug that tracing spans are not forwarded to spawned task. The
      problem was that only the telemetry span was forwarded. The solution to
      this is to use the tracing provided `in_current_span` to capture the
      current active span and pass the telemetry span explictely. We will now
      always enter the span when the future is polled. This is essentially the
      same strategy as tracing is doing with its `Instrumented`, but now
      extended for our use case with having multiple spans active.
      * More tests
      * Proper test for telemetry and prefix span
      * WIP
      * Fix test (need to create & enter the span at the same time)
      * WIP
      * Remove telemtry_span from sc_service config
      * CLEANUP
      * Update comment
      * Incorrect indent
      * More meaningful name
      * Dedent
      * Naming XD
      * Attempt to make a more complete test
      * lint
      * Missing licenses
      * Remove user data
      * CLEANUP
      * Apply suggestions from code review
      Co-authored-by: default avatarBastian Köcher <bkchr@users.noreply.github.com>
      * CLEANUP
      * Apply suggestion
      * Update bin/node/cli/tests/telemetry.rs
      Co-authored-by: David's avatarDavid <dvdplm@gmail.com>
      * Wrapping lines
      Co-authored-by: default avatarBastian Köcher <bkchr@users.noreply.github.com>
      Co-authored-by: David's avatarDavid <dvdplm@gmail.com>