Skip to content
Snippets Groups Projects
  1. Apr 30, 2022
  2. Apr 29, 2022
    • Nazar Mokrynskyi's avatar
      Network sync refactoring (part 1) (#11303) · af6773ab
      Nazar Mokrynskyi authored
      * Remove unnecessary imports, move one internal re-export into where it is actually used, make one import explicit
      
      * Move a few data structures down into modules
      
      * Use generic parameters in `sc-network` instead of `chain::Client` trait
      
      * Remove unnecessary bound
      af6773ab
    • Roman Proskuryakov's avatar
      Upgrade to libp2p 0.44.0 (#11009) · 887acda7
      Roman Proskuryakov authored
      * Update libp2p to 0.43.0, lru to 0.7.3
      
      * Fix websoket Incoming::Data
      
      * Rename ProtocolsHandler -> ConnectionHandler, remove inject_dis/connected, minor fixes
      
      * Fix args for inject_connection* callbacks
      
      * Fix DialPeer/DialAddress
      
      * Fix debug fmt
      
      * Add Endpoint to NetworkState
      
      * Fix Kad::get_record by key
      
      * Fix Sha2_256::digest
      
      * Fix IntoConnectionHandler
      
      * Fix borrowchk
      
      * Fix DialError::WrongPeerId
      
      * Remove NodeHandlerWrapperError
      
      * Fix KademliaEvent variants
      
      * Fix impl Add for String
      
      * Fix tabs in network_state
      
      * Apply cargo fmt
      
      * Fix a typo in req/resp
      
      * Fix tests
      
      * Fix peer_info:entry.info_expire
      
      * Fix PeerInfoBehaviour inject_address_change and inject_connection_closed
      
      * Patch libp2p to 0.44.0#6cc3b4e
      
      * Fix inject_connection_closed kad, req/resp
      
      * Apply cargo fmt
      
      * Use libp2p from crates.io
      
      * Fix review notes
      887acda7
  3. Apr 28, 2022
  4. Apr 27, 2022
  5. Apr 26, 2022
  6. Apr 25, 2022
  7. Apr 22, 2022
    • Bastian Köcher's avatar
      BABE: Fix aux data cleaning (#11263) · 53575a95
      Bastian Köcher authored
      With the latest optimizations of the `FinalityNotification` generation, the aux data pruning started
      to print a warning. The problem here was that we printed a warning and stopped the adding of blocks
      to prune when we hit the `heigh_limit`. This is now wrong, as we could for example have two 512 long
      forks and then we start finalizing one of them. The second fork head would be part of the stale
      heads at some point (in the current implementation when we finalize second fork head number + 1),
      but then we would actually need to go back into the past than `heigh_limit` (which was actually
      last_finalized - 1). We now go back until we reach the canonical chain.
      
      Also fixed some wrong comment that was added by be about the content of the `finalized` blocks in
      the `FinalityNotification`.
      53575a95
  8. Apr 21, 2022
  9. Apr 20, 2022
  10. Apr 19, 2022
  11. Apr 15, 2022
  12. Apr 14, 2022
  13. Apr 13, 2022
  14. Apr 12, 2022
    • Bastian Köcher's avatar
      Finality notification: Optimize calculation of stale heads (#11200) · cc4b5c48
      Bastian Köcher authored
      
      * Finality notification: Optimize calculation of stale heads
      
      While looking into some problem on Versi where a collator seemed to be stuck. I found out that it
      was not stuck but there was a huge gap between last finalized and best block. This lead to a lot
      leaves and it was basically trapped inside some loop of reading block headers from the db to find
      the stale heads. While looking into this I found out that `leaves` already supports the feature to
      give us the stale heads relative easily. However, the semantics change a little bit. Instead of
      returning all stale heads of blocks that are not reachable anymore after finalizing a block, we
      currently only return heads with a number lower than the finalized block. This should be no problem,
      because these other leaves that are stale will be returned later when a block gets finalized which
      number is bigger than the block number of these leaves.
      
      While doing that, I also changed `tree_route` of the `FinalityNotification` to include the
      `old_finalized`. Based on the comment I assumed that this was already part of it. However, if
      wanted, I can revert this change.
      
      * FMT
      
      * Update client/service/src/client/client.rs
      
      Co-authored-by: default avatarAndré Silva <123550+andresilva@users.noreply.github.com>
      
      * Do not include the last finalized block
      
      * Rename function
      
      * FMT
      
      * Fix tests
      
      * Update figure
      
      Co-authored-by: default avatarAndré Silva <123550+andresilva@users.noreply.github.com>
      cc4b5c48
  15. Apr 11, 2022
    • Koute's avatar
      Add new hardware and software metrics (#11062) · 8351ada6
      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`
      8351ada6
    • Bastian Köcher's avatar
      Prepare for rust stable 1.60 (#11138) · f517e57f
      Bastian Köcher authored
      
      * Prepare for rust stable 1.59
      
      Besides preparing the UI tests this also adds a new script update-rust-stable.sh script for
      simplifying the update of a rust stable version. This script will run all UI tests for the new
      rust stable version and updating the expected output.
      
      * Ensure we run the UI tests in CI
      
      * use staging ci image
      
      * More test updates
      
      * Unignore test (#11097)
      
      * empty commit for pipeline rerun
      
      * empty commit for pipeline rerun
      
      * Try to make clippy happy
      
      * More clippy fixes
      
      * FMT
      
      * ci image production
      
      Co-authored-by: default avataralvicsam <alvicsam@gmail.com>
      Co-authored-by: default avatarAlexander Samusev <41779041+alvicsam@users.noreply.github.com>
      f517e57f
    • Davide Galassi's avatar
      Normalization of CLI options format (CamelCase => kebab-case) (#11194) · 641a43a0
      Davide Galassi authored
      * Convert cli options from 'CamelCase' to 'kebab-case'
      * Remove not required 'as_str' for 'ExecutionStrategy' option
      641a43a0
  16. Apr 09, 2022
  17. Apr 08, 2022
  18. Apr 07, 2022
    • Niklas Adolfsson's avatar
      chore: update jsonrpsee to `v0.10.1` (#11173) · 1df943cd
      Niklas Adolfsson authored
      * fix(bin/node): remove unsed dep jsonrpsee
      
      * chore(remote ext): update jsonrpsee v0.10.1
      
      * chore(try runtime): update jsonrpsee v0.10.1
      
      * Update utils/frame/try-runtime/cli/src/commands/follow_chain.rs
      
      * cargo fmt
      1df943cd
  19. Apr 06, 2022
  20. Apr 05, 2022
  21. Apr 04, 2022
  22. Apr 03, 2022
  23. Mar 29, 2022