1. 12 Jan, 2021 7 commits
  2. 11 Jan, 2021 7 commits
  3. 08 Jan, 2021 3 commits
  4. 07 Jan, 2021 6 commits
  5. 06 Jan, 2021 9 commits
  6. 05 Jan, 2021 5 commits
    • Bastian Köcher's avatar
      Improve the `unbacked-span` (#2206) · 4f41fb74
      Bastian Köcher authored
      This ensures that we also record the first `import_statement` that will
      lead to the creation of the `unbacked-span`.
    • Peter Goodspeed-Niklaus's avatar
      Reduce the inclusion inherent's actual weight if the block is already heavy (#2060) · 0508b6f2
      Peter Goodspeed-Niklaus authored
      * don't modify inherent data on heavy block
      * write up current thinking on block weight detection
      * extract inherent inclusion check into its own function
      * put heavy block check into runtime
      * the `inclusion` inherent call is Operational, not Mandatory
      This resolves a lot of the trickiness about this issue, because
      we no longer need to override or supplant any existing proposer
      logic; the existing logic should exhibit these behaviors:
      - the `inclusion` inherent is prioritized over standard transactions
      - but if it's too heavy, i.e. in case of runtime upgrade, it'll be
        dropped in favor of that.
      It is my belief that allowing the proposer to just not include
      this data won't have any adverse effects: it's equivalent to replacing
      them with empty versions of themselves, which the `ProvideInherent`
      impl already does.
      * Revert "the `inclusion` inherent call is Operational, not Mandatory"
      This reverts commit e58858d1.
      * Revert "write up current thinking on block weight detection"
      This reverts commit fd587b80.
      * Revert "don't modify inherent data on heavy block"
      This reverts commit 38299d3c
      * add backed candidate block weight assumption to configuration
      * Limit backed candidates according to a candidate weight heuristic.
      This approach replaces making the inclusion inherent non-mandatory.
      It's still not ideal in that we have to configure a heuristic for
      how much each backed candidate 'weighs', instead of directly
      measuring it somehow.
      This approach also never truncates the signed bitfields. The
      rationale for that depends on some assumptions:
      - processing the signed bitfields is cheap compared to the
        backed candidates
      - it is beneficial to the progress of the relay chain
        to update the signed bitfields even if not all backed candidates
        are updated
      * simplify limit_backed_candidates and weight assumption
      * don't trust the provisioner to fairly distribute candidates
      * use saturating subtraction
      * empty commit to restart ci
      * use new mechanism for getting max block weight
      * apply weight refunds to the inclusion inherent
      This makes some assumptions about fundamental weights, which are
      encapsulated as constants. From there, it lets Substrate know
      what the actual computed weight of the inherent is.
      * use a correct fixed weight for the inclusion inherent
      Co-authored-by: thiolliere's avatarGuillaume Thiolliere <gui.thiolliere@gmail.com>
      * use dynamic inclusion weight so we reduce calculated weight when excluding candidates
      * don't double-count this intrinsic's weight in the block weight
      * add unit tests of fn limit_backed_candidates
      * add tests that the inclusion inherent's weight correctly updates
      Co-authored-by: thiolliere's avatarGuillaume Thiolliere <gui.thiolliere@gmail.com>
    • dependabot[bot]'s avatar
    • Bastian Köcher's avatar
      Add one Jaeger span per relay parent (#2196) · 17344327
      Bastian Köcher authored
      * Add one Jaeger span per relay parent
      This adds one Jaeger span per relay parent, instead of always creating
      new spans per relay parent. This should improve the UI view, because
      subsystems are now grouped below one common span.
      * Fix doc tests
      * Replace `PerLeaveSpan` to `PerLeafSpan`
      * More renaming
      * Moare
      * Update node/subsystem/src/lib.rs
      Co-authored-by: Andronik Ordian's avatarAndronik Ordian <write@reusable.software>
      * Skip the spans
      * Increase `spec_version`
      Co-authored-by: Andronik Ordian's avatarAndronik Ordian <write@reusable.software>
    • Sergey Pepyakin's avatar
      Parachains well known keys and abridged primitives (#2194) · 6b688dd5
      Sergey Pepyakin authored
      * Add well_known_keys
      * Reorder HrmpChannel and HostConfiguration members
      * abridged versions and well known keys tests
      * Add some comments
      * Add a note on generation of the prefixes
      and other magic values
      * Recommend accessing the well known values through abridged structs
  7. 04 Jan, 2021 3 commits
    • Bastian Köcher's avatar
      Use correct ROC currency name (#2195) · e8cd587d
      Bastian Köcher authored
    • asynchronous rob's avatar
      Improve Network Spans (#2169) · a891884e
      asynchronous rob authored
      * utility functions for erasure-coding threshold
      * add candidate-hash tag to candidate jaeger spans
      * debug implementation for jaeger span
      * add a span to each live candidate in availability dist.
      * availability span covers only our piece
      * fix tests
      * keep span alive slightly longer
      * remove spammy bitfield-gossip-received log
      * Revert "remove spammy bitfield-gossip-received log"
      This reverts commit 831a2db5
      * add claimed validator to bitfield-gossip span
      * add peer-id to handle-incoming span
      * add peer-id to availability distribution span
      * Update node/network/availability-distribution/src/lib.rs
      Co-authored-by: default avatarBernhard Schuster <bernhard@ahoi.io>
      * Update erasure-coding/src/lib.rs
      Co-authored-by: default avatarBernhard Schuster <bernhard@ahoi.io>
      * Update node/subsystem/src/jaeger.rs
      Co-authored-by: default avatarBernhard Schuster <bernhard@ahoi.io>
      Co-authored-by: default avatarBernhard Schuster <bernhard@ahoi.io>
    • Sergey Pepyakin's avatar
      Add relay storage root to persisted validation data (#2161) · 50538aa5
      Sergey Pepyakin authored
      * Cont.: Implement the state root obtaining during inclusion
      During inclusion now we obtain the storage root by passing it through
      the inclusion_inherent.
      * Fix tests
      * Bump rococo spec version
      * Reorder the parent header into the end
      of the inclusion inherent.
      When the parent header is in the beginning, it shifts the other two
      fields, so that a previous version won't be able to decode that. If
      we put the parent header in the end, the other two fields will stay
      at their positions, thus make it possible to decode with the previous
      That allows us to perform upgrade of rococo runtime without needing of
      simultanuous upgrade of nodes and runtime, or restart of the network.
      * Squash a stray tab