1. 14 Jan, 2021 5 commits
  2. 13 Jan, 2021 7 commits
    • asynchronous rob's avatar
      scheduler: handle re-scheduling around finalization correctly (#2257) · 9115d427
      asynchronous rob authored
      * scheduler: handle re-scheduling around finalization correctly
      * also make sure parathreads get cleaned
      * run scheduling in finalization
      * Remove stray println!
      * Update the schedule call site in inclusion inherent
      * Clarify subtlety around SessionStartBlock
      * Remove double semi-colon
      * reschedule prior to `availability_cores` and in on-initialize
      * improve docs
      * fix line
      * more doc reformat
      * remove unneeded call
      * avoid unnecessary scheduling on initialize
      * split `clear` and `schedule
      * Update runtime/parachains/src/scheduler.rs
      Co-authored-by: Sergey Pepyakin's avatarSergei Shulepov <sergei@parity.io>
      Co-authored-by: Sergey Pepyakin's avatarSergei Shulepov <sergei@parity.io>
    • Bernhard Schuster's avatar
      display errors with their sources (#2264) · 2fd345b8
      Bernhard Schuster authored
      * update futures to 0.3.9
      * companion changes for generic error types
      * improve errors, keep error sources
      * command compile fix
      * use the correct Error type, add annotation
      * avoid async { fut.await.map_err(E::Variant) } with TryFuture
      * fix cargo lock, bump futures to 0.3.10
      futures 0.3.9 got yanked
      * chore cargo update -p sp-io
      * minor quirk
      * make rustc 1.48 happy by bouning the error more tightly
      * be more explicit
      * cargo lock futures
    • Sergey Pepyakin's avatar
    • Andronik Ordian's avatar
      Companion for substrate#7892 (#2262) · e5ee5748
      Andronik Ordian authored
      * session_info: use correct authorities set
      * bump rococo spec_version to 19
      * "Update Substrate"
      Co-authored-by: parity-processbot <>
    • Bernhard Schuster's avatar
      metered mpsc channels (#2235) · e3676fdc
      Bernhard Schuster authored
    • Sergey Pepyakin's avatar
      HRMP channel deposits (#2225) · 4489b528
      Sergey Pepyakin authored
      * Drive by fixes
      The visibility modifiers are remnants of the previous structure where
      HRMP wasn't a standalone module, by rather a submodule of the router
      * Add Currency assoc type to Config
      This would allow us to reserve balance for deposits. This commit also
      integrates the HRMP module in rococo, test-runtime and mocks to use the
      balances pallet.
      * Fix a bug that doesn't increment the age
      In case the request is not confirmed, the age would be incremented but
      not persisted.
      * Fix cleaning the indexes
      Before that change, the cleaning of the channel indexes was wrong, because it
      naively removed entire rows that was pertaining to the para we delete.
      This approach is flawed because it doesn't account for the rows that are
      pertaining to other paras that contain the outgoing one.
      This clearly violates the invariant imposed on the indexes, that all
      the index rows must contain alive paras, but apart from that it also
      lead to the situation where ingress index would contain the a different
      set of channels that an egress have.
      * Reserve currency for opening the channels
      Note the ugly `unique_saturated_into` calls. The reason for them is the
      currency trait accepts and defines the `Balance` associated type and the
      deposit values are coming from the `HostConfiguration` where they are
      defined using the `Balance`.
      I figured that parameterising `HostConfiguration` would be annoying. On
      the other hand, I don't expect these `unique_saturated_into` calls to
      give us problems since it seems to be a reasonable assumption that this
      module will be instantiated within a runtime where the Currency provided
      will have a Balance that matches the one used in the configuration.
      * Tests: Adapt `run_to_block` so that it submits a proper config
      * Tests: exercise the deposit logic
    • Sergey Pepyakin's avatar
      Avoid inlining `update_config_member` (#2246) · d0703258
      Sergey Pepyakin authored
      Closes #2241
  3. 12 Jan, 2021 7 commits
  4. 11 Jan, 2021 7 commits
  5. 08 Jan, 2021 3 commits
  6. 07 Jan, 2021 6 commits
  7. 06 Jan, 2021 5 commits
    • Andronik Ordian's avatar
      upgrade a few dependencies (companion for 7831) (#2205) · e9866d55
      Andronik Ordian authored
      * upgrade a few dependencies
      * "Update Substrate"
      Co-authored-by: parity-processbot <>
    • Denis_P's avatar
      CI: remove squash and fix buildah push (#2212) · 51d55338
      Denis_P authored
    • Pierre Krieger's avatar
      Make order consistent (#2215) · 107673eb
      Pierre Krieger authored
    • felix's avatar
      added new bootnode to chain spec's (#2204) · 00c1ef88
      felix authored
      * added new bootnode to chain spec's
      * remove trailing newline
    • Peter Goodspeed-Niklaus's avatar
      Add metrics timing message passing from OverseerSubsystemContext to Overseer::route_message (#2201) · 004dc50d
      Peter Goodspeed-Niklaus authored
      * add timing setup to OverseerSubsystemContext
      * figure out how to initialize the rng
      * attach a timer to a portion of the messages traveling to the Overseer
      This timer only exists / logs a fraction of the time (configurable
      by `MESSAGE_TIMER_METRIC_CAPTURE_RATE`). When it exists, it tracks
      the span between the `OverSubsystemContext` receiving the message
      and its receipt in `Overseer::run`.
      * propagate message timing to the start of route_message
      This should be more accurate; it ensures that the timer runs
      at least as long as that function. As `route_message` is async,
      it may not actually run for some time after it is called (or ever).
      * fix failing test
      * rand_chacha apparently implicitly has getrandom feature
      * change rng initialization
      The previous impl using `from_entropy` depends on the `getrandom`
      crate, which uses the system entropy source, and which does not
      work on `wasm32-unknown-unknown` because it wants to fall back to
      a JS implementation which we can't assume exists.
      This impl depends only on `rand::thread_rng`, which has no documentation
      stating that it's similarly limited.
      * remove randomness in favor of a simpler 1 of N procedure
      This deserves a bit of explanation, as the motivating issue explicitly
      requested randomness. In short, it's hard to get randomness to compile
      for `wasm32-unknown-unknown` because that is explicitly intended to be
      as deterministic as practical. Additionally, even though it would never
      be used for consensus purposes, it still felt offputting to intentionally
      introduce randomness into a node's operations. Except, it wasn't really
      random, either: it was a deterministic PRNG varying only in its state,
      and getting the state to work right for that target would have required
      initializing from a constant.
      Given that it was a deterministic sequence anyway, it seemed much simpler
      and more explicit to simply select one of each N messages instead of
      attempting any kind of realistic randomness.
      * reinstate randomness for better statistical properties
      This partially reverts commit 0ab8594c.
      `oorandom` is much lighter than the previous `rand`-based implementation,
      which makes this easier to work with.
      This implementation gives each subsystem and each child RNG a distinct
      increment, which should ensure they produce distinct streams of values.