Skip to content
  1. Dec 09, 2020
  2. Dec 08, 2020
  3. Dec 07, 2020
  4. Dec 06, 2020
  5. Dec 04, 2020
    • Shawn Tabrizi's avatar
      Add Standard Error to Weight Template (#7652) · 39278096
      Shawn Tabrizi authored
      * Add standard error to weight template
      
      * fix test compile
      39278096
    • Gavin Wood's avatar
      Features needed for reserve-backed stablecoins (#7152) · 18022834
      Gavin Wood authored
      
      
      * Features needed for reserve-backed stablecoins
      
      * Builds & tests.
      
      * Double map for an efficient destroy.
      
      * Update frame/assets/src/lib.rs
      
      Co-authored-by: default avatarNikolay Volf <[email protected]>
      
      * ED/zombie-count/refs
      
      Feature: ED/minimum balance enforcement
      Feature: enforce zombie count
      Feature: allow system-alive accounts to exist, but add reference
      
      * Update frame/assets/src/lib.rs
      
      Co-authored-by: default avatarNikolay Volf <[email protected]>
      
      * Update frame/assets/Cargo.toml
      
      Co-authored-by: default avatarNiklas Adolfsson <[email protected]>
      
      * Docs
      
      * Some tests
      
      * More tests
      
      * Allow for max_zombies to be adjusted
      
      * Test for set_max_zombies
      
      * Tests and a couple of fixes
      
      * First few benchmarks
      
      * Benchmarks.
      
      * Fix error message in test
      
      * Fixes
      
      * Fixes
      
      * Fixes
      
      * cargo run --release --features runtime-benchmarks --manifest-path bin/node/cli/Cargo.toml -- benchmark --chain dev --steps 50 --repeat 20 --extrinsic * --execution=wasm --wasm-execution=compiled --output ./bin/node/runtime/src/weights --header ./HEADER --pallet pallet_assets
      
      * Update frame/assets/src/lib.rs
      
      Co-authored-by: default avatarGuillaume Thiolliere <[email protected]>
      
      * Fixes
      
      * Fixes
      
      * Fixes
      
      * cargo run --release --features runtime-benchmarks --manifest-path bin/node/cli/Cargo.toml -- benchmark --chain dev --steps 50 --repeat 20 --extrinsic * --execution=wasm --wasm-execution=compiled --output ./bin/node/runtime/src/weights --header ./HEADER --pallet pallet_assets
      
      * Fixes
      
      * Update default weight
      
      * Add proper verification to benchmarks
      
      * minor improvements to tests
      
      * Update frame/assets/src/benchmarking.rs
      
      Co-authored-by: default avatarKian Paimani <[email protected]>
      
      * Fix
      
      * New weights system
      
      * fix compile
      
      * cargo run --release --features=runtime-benchmarks --manifest-path=bin/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_assets --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/assets/src/weights.rs --template=./.maintain/frame-weight-template.hbs
      
      Co-authored-by: default avatarNikolay Volf <[email protected]>
      Co-authored-by: default avatarNiklas Adolfsson <[email protected]>
      Co-authored-by: default avatarParity Benchmarking Bot <[email protected]>
      Co-authored-by: default avatarGuillaume Thiolliere <[email protected]>
      Co-authored-by: default avatarShawn Tabrizi <[email protected]>
      Co-authored-by: default avatarKian Paimani <[email protected]>
      18022834
  6. Dec 03, 2020
    • Bastian Köcher's avatar
      Don't panic on a sink error (#7666) · f73ac5eb
      Bastian Köcher authored
      f73ac5eb
    • Bastian Köcher's avatar
      Use block requests to check if block responses are correct (#7653) · 864ce58c
      Bastian Köcher authored
      * Use block requests to check if block responses are correct
      
      Before this pr sync relied on recently announced blocks to check if a
      given peer response is correct. However this could lead to situations
      where we requested a block from a peer and it gave us the requested, but
      we rejected the response because this peer never send us an announcement
      for the given block. See the added tests for a reproduction of the
      problem.
      With this pr, we now take the block request to check if a given response
      matches the request. A node should not send us a block response
      without a request anyway.
      
      Essentially there is still a bug, because as you see in the test, we are
      requesting block 2, while we already have this block imported. It even
      happens that we request a block from the network that we have authored.
      However a fix for this would require some more refactoring of the sync code.
      
      * Revert change
      
      * Give the test a proper name
      
      * Add moar logging
      
      * Move cheaper checks
      
      * Move checks to common place
      864ce58c