Skip to content
Snippets Groups Projects
  1. Aug 28, 2024
    • Pankaj's avatar
      Remove pallet::getter usage from treasury (#4962) · 4096ad7f
      Pankaj authored
      
      ISSUE
      Link to the issue:
      https://github.com/paritytech/polkadot-sdk/issues/3326
      
      Deliverables
      
      [Deprecation] remove pallet::getter usage from pallet-treasury
      
      ---------
      
      Co-authored-by: default avatarOliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
      Co-authored-by: default avatarDónal Murray <donal.murray@parity.io>
      Co-authored-by: default avatarDónal Murray <donalm@seadanda.dev>
      Co-authored-by: default avatarBastian Köcher <git@kchr.de>
    • dependabot[bot]'s avatar
      Bump blake2b_simd from 1.0.1 to 1.0.2 (#5404) · 94237181
      dependabot[bot] authored
      
      Bumps [blake2b_simd](https://github.com/oconnor663/blake2_simd) from
      1.0.1 to 1.0.2.
      <details>
      <summary>Commits</summary>
      <ul>
      <li><a
      href="https://github.com/oconnor663/blake2_simd/commit/1dfcf325200cf281d9313ae79734c828d914d241"><code>1dfcf32</code></a>
      version 1.0.2</li>
      <li><a
      href="https://github.com/oconnor663/blake2_simd/commit/b66d6b5124e7568bbb92f8a1f22e043ac8cded25"><code>b66d6b5</code></a>
      Bump constant_time_eq to 0.3 and MSRV to 1.66</li>
      <li><a
      href="https://github.com/oconnor663/blake2_simd/commit/d9ce189cb98e00b0a0653d8a9586ff12e5774202"><code>d9ce189</code></a>
      stop using MIPS for big-endian testing</li>
      <li><a
      href="https://github.com/oconnor663/blake2_simd/commit/9d338b55992a5e6a0411e2da7153ec654f70b213"><code>9d338b5</code></a>
      use <code>avoid-dev-deps</code> for the MSRV test</li>
      <li><a
      href="https://github.com/oconnor663/blake2_simd/commit/c347f493365a82bc4472a05609c68a1152439b44"><code>c347f49</code></a>
      update the assert_cmd test dependency to v2.0.8</li>
      <li>See full diff in <a
      href="https://github.com/oconnor663/blake2_simd/compare/1.0.1...1.0.2">compare
      view</a></li>
      </ul>
      </details>
      <br />
      
      
      [![Dependabot compatibility
      score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=blake2b_simd&package-manager=cargo&previous-version=1.0.1&new-version=1.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
      
      Dependabot will resolve any conflicts with this PR as long as you don't
      alter it yourself. You can also trigger a rebase manually by commenting
      `@dependabot rebase`.
      
      [//]: # (dependabot-automerge-start)
      [//]: # (dependabot-automerge-end)
      
      ---
      
      <details>
      <summary>Dependabot commands and options</summary>
      <br />
      
      You can trigger Dependabot actions by commenting on this PR:
      - `@dependabot rebase` will rebase this PR
      - `@dependabot recreate` will recreate this PR, overwriting any edits
      that have been made to it
      - `@dependabot merge` will merge this PR after your CI passes on it
      - `@dependabot squash and merge` will squash and merge this PR after
      your CI passes on it
      - `@dependabot cancel merge` will cancel a previously requested merge
      and block automerging
      - `@dependabot reopen` will reopen this PR if it is closed
      - `@dependabot close` will close this PR and stop Dependabot recreating
      it. You can achieve the same result by closing it manually
      - `@dependabot show <dependency name> ignore conditions` will show all
      of the ignore conditions of the specified dependency
      - `@dependabot ignore this major version` will close this PR and stop
      Dependabot creating any more for this major version (unless you reopen
      the PR or upgrade to it yourself)
      - `@dependabot ignore this minor version` will close this PR and stop
      Dependabot creating any more for this minor version (unless you reopen
      the PR or upgrade to it yourself)
      - `@dependabot ignore this dependency` will close this PR and stop
      Dependabot creating any more for this dependency (unless you reopen the
      PR or upgrade to it yourself)
      
      
      </details>
      
      Signed-off-by: default avatardependabot[bot] <support@github.com>
      Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    • dependabot[bot]'s avatar
      Bump rustversion from 1.0.14 to 1.0.17 (#5405) · f7e0ecc5
      dependabot[bot] authored
      
      Bumps [rustversion](https://github.com/dtolnay/rustversion) from 1.0.14
      to 1.0.17.
      <details>
      <summary>Release notes</summary>
      <p><em>Sourced from <a
      href="https://github.com/dtolnay/rustversion/releases">rustversion's
      releases</a>.</em></p>
      <blockquote>
      <h2>1.0.17</h2>
      <ul>
      <li>Support Windows builds that have OUT_DIR prefixed with
      <code>\\?\</code> (<a
      href="https://redirect.github.com/dtolnay/rustversion/issues/51">#51</a>)</li>
      </ul>
      <h2>1.0.16</h2>
      <ul>
      <li>Resolve unexpected_cfgs warning (<a
      href="https://redirect.github.com/dtolnay/rustversion/issues/48">#48</a>)</li>
      </ul>
      <h2>1.0.15</h2>
      <ul>
      <li>Recognize $RUSTC_WRAPPER environment variable (<a
      href="https://redirect.github.com/dtolnay/rustversion/issues/47">#47</a>)</li>
      </ul>
      </blockquote>
      </details>
      <details>
      <summary>Commits</summary>
      <ul>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/adb11fa32295a5d3df7b742e545f4e9b776f9bb3"><code>adb11fa</code></a>
      Release 1.0.17</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/875982000ea11f59a67564bf34c6f3255935b6e2"><code>8759820</code></a>
      Merge pull request <a
      href="https://redirect.github.com/dtolnay/rustversion/issues/51">#51</a>
      from dtolnay/windows</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/cfafcd5906e6020ae67014e33a84446824301c95"><code>cfafcd5</code></a>
      Support OUT_DIR located in \?\ path on Windows</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/c7bc274d96fbde0fe3b3fd5a4a9ea1e0215b0ddb"><code>c7bc274</code></a>
      Release 1.0.16</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/746bf5af0dc5423574982ba2f479190b643c98fe"><code>746bf5a</code></a>
      Merge pull request <a
      href="https://redirect.github.com/dtolnay/rustversion/issues/48">#48</a>
      from dtolnay/checkcfg</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/84f01fa8d731c51842848a4e4d27750cefd879e0"><code>84f01fa</code></a>
      Resolve unexpected_cfgs warning</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/70ca5ad8a2aba79053be803a4e70156b46e44028"><code>70ca5ad</code></a>
      Release 1.0.15</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/0fa74f583b1fff92ed6f48acad6509428f44ed1a"><code>0fa74f5</code></a>
      Merge pull request <a
      href="https://redirect.github.com/dtolnay/rustversion/issues/47">#47</a>
      from dtolnay/rustcwrapper</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/51f46e2d2281dce75a8e4d46c0ed55f2ae3c4e33"><code>51f46e2</code></a>
      Apply RUSTC_WRAPPER</li>
      <li><a
      href="https://github.com/dtolnay/rustversion/commit/df7e51d0f01e06b2212c96f26cd04af5c59e1e39"><code>df7e51d</code></a>
      Explicitly install a Rust toolchain for cargo-outdated job</li>
      <li>Additional commits viewable in <a
      href="https://github.com/dtolnay/rustversion/compare/1.0.14...1.0.17">compare
      view</a></li>
      </ul>
      </details>
      <br />
      
      
      [![Dependabot compatibility
      score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=rustversion&package-manager=cargo&previous-version=1.0.14&new-version=1.0.17)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
      
      Dependabot will resolve any conflicts with this PR as long as you don't
      alter it yourself. You can also trigger a rebase manually by commenting
      `@dependabot rebase`.
      
      [//]: # (dependabot-automerge-start)
      [//]: # (dependabot-automerge-end)
      
      ---
      
      <details>
      <summary>Dependabot commands and options</summary>
      <br />
      
      You can trigger Dependabot actions by commenting on this PR:
      - `@dependabot rebase` will rebase this PR
      - `@dependabot recreate` will recreate this PR, overwriting any edits
      that have been made to it
      - `@dependabot merge` will merge this PR after your CI passes on it
      - `@dependabot squash and merge` will squash and merge this PR after
      your CI passes on it
      - `@dependabot cancel merge` will cancel a previously requested merge
      and block automerging
      - `@dependabot reopen` will reopen this PR if it is closed
      - `@dependabot close` will close this PR and stop Dependabot recreating
      it. You can achieve the same result by closing it manually
      - `@dependabot show <dependency name> ignore conditions` will show all
      of the ignore conditions of the specified dependency
      - `@dependabot ignore this major version` will close this PR and stop
      Dependabot creating any more for this major version (unless you reopen
      the PR or upgrade to it yourself)
      - `@dependabot ignore this minor version` will close this PR and stop
      Dependabot creating any more for this minor version (unless you reopen
      the PR or upgrade to it yourself)
      - `@dependabot ignore this dependency` will close this PR and stop
      Dependabot creating any more for this dependency (unless you reopen the
      PR or upgrade to it yourself)
      
      
      </details>
      
      Signed-off-by: default avatardependabot[bot] <support@github.com>
      Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    • Serban Iorga's avatar
      Bridge zombienet tests: remove old command (#5434) · edd6f717
      Serban Iorga authored
      Related to: https://github.com/paritytech/polkadot-sdk/issues/3176
      
      This PR:
      - migrates test 0003 to the new bridges zombienet tests command
      **This test didn't work before and it still doesn't work. It was added
      at a time when we couldn't run it because we didn't have the scafolding.
      It needs to be fixed. For the moment we keep it in the repo as it is
      since the idea has value. But we don't run it in the CI. We can also
      decide to remove it in the future**
      - removes the old command for running bridge zombienet tests
      - updates the README
    • Serban Iorga's avatar
      polkadot-parachain: Add omni-node variant with u64 block number (#5269) · c4ced11f
      Serban Iorga authored
      Related to https://github.com/paritytech/polkadot-sdk/issues/4787
      
      The main changes in this PR are the following:
      - making the NodeSpec logic generic on the Block type
      - adding an omni-node variant with u64 block number
      
      Apart from this, the PR also moves some of the logic in `service.rs` to
      the `common` subfolder
      
      The omni-node variant with u64 block number is not used yet. We have to
      either expose the option in the CLI or to read the block number from the
      chain spec somehow. Will do it in a future PR.
    • thiolliere's avatar
      Refactor verbose test (#5506) · 97fa922c
      thiolliere authored
      A test is triggering a log error. But is correct and successful. This is
      a refactor without triggering the log error.
    • PG Herveou's avatar
    • A Ahmad's avatar
      IBP Coretime Polkadot bootnodes (#5499) · ef3a0d8f
      A Ahmad authored
      ✄
      -----------------------------------------------------------------------------
      
      Thank you for your Pull Request! :pray:
      
       Please make sure it follows the
      contribution guidelines outlined in [this
      
      document](https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/CONTRIBUTING.md)
      and fill out the
      sections below. Once you're ready to submit your PR for review, please
      delete this section and leave only the text under
      the "Description" heading.
      
      # Description
      
      *A concise description of what your PR is doing, and what potential
      issue it is solving. Use [Github semantic
      
      linking](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
      to link the PR to an issue that must be closed once this is merged.*
      
      ## Integration
      
      *In depth notes about how this PR should be integrated by downstream
      projects. This part is mandatory, and should be
      reviewed by reviewers, if the PR does NOT have the `R0-Silent` label. In
      case of a `R0-Silent`, it can be ignored.*
      
      ## Review Notes
      
      *In depth notes about the **implementation** details of your PR. This
      should be the main guide for reviewers to
      understand your approach and effectively review it. If too long, use
      
      [`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details)*.
      
      *Imagine that someone who is depending on the old code wants to
      integrate your new code and the only information that
      they get is this section. It helps to include example usage and default
      value here, with a `diff` code-block to show
      possibly integration.*
      
      *Include your leftover TODOs, if any, here.*
      
      # Checklist
      
      * [ ] My PR includes a detailed description as outlined in the
      "Description" and its two subsections above.
      * [ ] My PR follows the [labeling requirements](
      
      https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/CONTRIBUTING.md#Process
      ) of this project (at minimum one label for `T` required)
      * External contributors: ask maintainers to put the right label on your
      PR.
      * [ ] I have made corresponding changes to the documentation (if
      applicable)
      * [ ] I have added tests that prove my fix is effective or that my
      feature works (if applicable)
      
      You can remove the "Checklist" section once all have been checked. Thank
      you for your contribution!
      
      ✄
      -----------------------------------------------------------------------------
      
      Co-authored-by: default avatarDónal Murray <donal.murray@parity.io>
    • Niklas Adolfsson's avatar
      rpc server: listen to `ipv6 socket` if available and... · 09254eb9
      Niklas Adolfsson authored
      rpc server: listen to `ipv6 socket` if available and `--experimental-rpc-endpoint` CLI option (#4792)
      
      Close https://github.com/paritytech/polkadot-sdk/issues/3488,
      https://github.com/paritytech/polkadot-sdk/issues/4331
      
      This changes/adds the following:
      
      1. The default setting is that substrate starts a rpc server that
      listens to localhost both Ipv4 and Ipv6 on the same port. Ipv6 is
      allowed to fail because some platforms may not support it
      2. A new RPC CLI option `--experimental-rpc-endpoint` which allow to
      configure arbitrary listen addresses including the port, if this is
      enabled no other interfaces are enabled.
      3. If the local addr is not found for any of the sockets the server is
      not started throws an error.
      4. Remove the deny_unsafe from the RPC implementations instead this is
      an extension to allow different polices for different interfaces/sockets
      such one may enable unsafe on local interface and safe on only the
      external interface.
      
      So for instance in this PR it's now possible to start up three RPC
      endpoints as follows:
      ```
      $ polkadot --experimental-rpc-endpoint "listen-addr=127.0.0.1:9944,rpc-methods=unsafe" --experimental-rpc-endpoint "listen-addr=0.0.0.0:9945,rpc-methods=safe,rate-limit=100" --experimental-rpc-endpoint "listen-addr=[::1]:9944,optional=true"
      ```
      
      #### Needs to be addressed
      
      ~1. Support binding to a random port if it's fails with the default
      stuff for backward compatible reasons~
      ~2. How to sync that the rpc CLI params and that the rpc-listen-addr
      align, hard to maintain...~
      ~3. Add similar warning prints for exposing unsafe methods on external
      interfaces..~
      ~4. Inline todos + the hacky String conversion from rpc params.~
      
      #### Cons with this PR
      
      Manual strings parsing impl more error-prone than relying on clap....
      
      //cc @jsdw @BulatSaif @PierreBesson @bkchr
      
      
      
      ---------
      
      Co-authored-by: default avatarSebastian Kunert <skunert49@gmail.com>
    • Alexandru Gheorghe's avatar
      Update approval-voting-regression-bench (#5504) · f0fd083e
      Alexandru Gheorghe authored
      
      The accepted divergence rate of 1/1000 is excessive and leads to false
      positives especially after
      https://github.com/paritytech/polkadot-sdk/pull/4772 and
      https://github.com/paritytech/polkadot-sdk/pull/5042, so let's increase
      it to 1/100 since we do have some randomness in the system and there is
      no point in being that strict.
      
      Fixes: https://github.com/paritytech/polkadot-sdk/issues/5463
      
      ---------
      
      Signed-off-by: default avatarAlexandru Gheorghe <alexandru.gheorghe@parity.io>
    • Arsham Teymouri's avatar
      change try-runtime rpc domains (#5443) · f4be48cf
      Arsham Teymouri authored
      
      as part of paritytech/devops/3502, try-runtime nodes were migrated to a
      new provider with a new domain address. The PR fixes all the references
      to try-runtime nodes on rococo, westend, kusama and polkadot networks.
      
      ---------
      
      Co-authored-by: default avatarArshamTeymouri <ArshamTeymouri@users.noreply.github.com>
      Co-authored-by: default avatarOliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
      Co-authored-by: default avatarNiklas Adolfsson <niklasadolfsson1@gmail.com>
    • Serban Iorga's avatar
      polkadot-parachain-bin: Remove contracts parachain (#5471) · 38fce088
      Serban Iorga authored
      Related to: https://github.com/paritytech/polkadot-sdk/issues/5210
      
      Follow-up for https://github.com/paritytech/polkadot-sdk/pull/5288, as
      per this comment:
      https://github.com/paritytech/polkadot-sdk/pull/5288#discussion_r1711157476
      
      I hope I understood this correctly.
  2. Aug 27, 2024
    • s0me0ne-unkn0wn's avatar
      Add feature to allow Aura collator to use full PoV size (#5393) · f90bfa6a
      s0me0ne-unkn0wn authored
      
      This PR introduces a feature that allows to optionally enable using the
      full PoV size.
      
      Technically, we're ready to enable it by default, but as corresponding
      runtime changes have not been propagated to the system parachain
      runtimes yet, doing so could put them at risk. On the other hand, there
      are teams that could benefit from it right now, and it makes no sense
      for them to wait for the fellowship release and everything.
      
      ---------
      
      Co-authored-by: default avatarAndrei Sandu <54316454+sandreim@users.noreply.github.com>
    • Frazz's avatar
      Adding stkd bootnodes (#5470) · 7a2c5375
      Frazz authored
      Opening this PR to add our bootnodes for the IBP. These nodes are
      located in Santiago Chile, we own and manage the underlying hardware. If
      you need any more information please let me know.
      
      
      Commands to test:
      
      ```
      ./polkadot --tmp --name "testing-bootnode" --chain kusama --reserved-only --reserved-nodes "/dns/kusama.bootnode.stkd.io/tcp/30633/wss/p2p/12D3KooWJHhnF64TXSmyxNkhPkXAHtYNRy86LuvGQu1LTi5vrJCL" --no-hardware-benchmarks
      
      ./polkadot --tmp --name "testing-bootnode" --chain paseo --reserved-only --reserved-nodes "/dns/paseo.bootnode.stkd.io/tcp/30633/wss/p2p/12D3KooWMdND5nwfCs5M2rfp5kyRo41BGDgD8V67rVRaB3acgZ53" --no-hardware-benchmarks
      
      ./polkadot --tmp --name "testing-bootnode" --chain polkadot --reserved-only --reserved-nodes "/dns/polkadot.bootnode.stkd.io/tcp/30633/wss/p2p/12D3KooWEymrFRHz6c17YP3FAyd8kXS5gMRLgkW4U77ZJD2ZNCLZ" --no-hardware-benchmarks
      
      ./polkadot --tmp --name "testing-bootnode" --chain westend --reserved-only --reserved-nodes "/dns/westend.bootnode.stkd.io/tcp/30633/wss/p2p/12D3KooWHaQKkJiTPqeNgqDcW7dfYgJxYwT8YqJMtTkueSu6378V" --no-hardware-benchmarks
      ```
    • Parth's avatar
      Make `PendingConfigs` storage item public (#5467) · 0d7becf2
      Parth authored
      
      ## Description
      This PR changes `PendingConfigs` storage item's visibility from crate to
      public. This enable us to read it in our runtime.
      
      ---------
      
      Co-authored-by: default avatarBastian Köcher <git@kchr.de>
    • Oliver Tale-Yazdi's avatar
      frame-omni-bencher maintenance (#5466) · 7e7c3345
      Oliver Tale-Yazdi authored
      
      Changes:
      - Set default level to `Info` again. Seems like a dependency update set
      it to something higher.
      - Fix docs to not use `--locked` since we rely on dependency bumps via
      cargo.
      - Add README with rust docs.
      - Fix bug where the node ignored `--heap-pages` argument.
      
      You can test the `--heap-pages` bug by running this command on master
      and then on this branch. Note that it should fail because of the very
      low heap pages arg:
      `cargo run --release --bin polkadot --features=runtime-benchmarks --
      benchmark pallet --chain=dev --steps=10 --repeat=30
      --wasm-execution=compiled --heap-pages=8 --pallet=frame-system
      --extrinsic="*"`
      
      ---------
      
      Signed-off-by: default avatarOliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
      Co-authored-by: default avatarggwpez <ggwpez@users.noreply.github.com>
    • dependabot[bot]'s avatar
      Bump the ci_dependencies group across 1 directory with 2 updates (#5401) · 33010098
      dependabot[bot] authored
      
      Bumps the ci_dependencies group with 2 updates in the / directory:
      [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action)
      and
      [docker/build-push-action](https://github.com/docker/build-push-action).
      
      Updates `docker/setup-buildx-action` from 3.5.0 to 3.6.1
      <details>
      <summary>Release notes</summary>
      <p><em>Sourced from <a
      href="https://github.com/docker/setup-buildx-action/releases">docker/setup-buildx-action's
      releases</a>.</em></p>
      <blockquote>
      <h2>v3.6.1</h2>
      <ul>
      <li>Check for malformed docker context by <a
      href="https://github.com/crazy-max"><code>@​crazy-max</code></a> in <a
      href="https://redirect.github.com/docker/setup-buildx-action/pull/347">docker/setup-buildx-action#347</a></li>
      </ul>
      <p><strong>Full Changelog</strong>: <a
      href="https://github.com/docker/setup-buildx-action/compare/v3.6.0...v3.6.1">https://github.com/docker/setup-buildx-action/compare/v3.6.0...v3.6.1</a></p>
      <h2>v3.6.0</h2>
      <ul>
      <li>Create temp docker context if default one has TLS data loaded before
      creating a container builder by <a
      href="https://github.com/crazy-max"><code>@​crazy-max</code></a> in <a
      href="https://redirect.github.com/docker/setup-buildx-action/pull/341">docker/setup-buildx-action#341</a></li>
      </ul>
      <p><strong>Full Changelog</strong>: <a
      href="https://github.com/docker/setup-buildx-action/compare/v3.5.0...v3.6.0">https://github.com/docker/setup-buildx-action/compare/v3.5.0...v3.6.0</a></p>
      </blockquote>
      </details>
      <details>
      <summary>Commits</summary>
      <ul>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/988b5a0280414f521da01fcc63a27aeeb4b104db"><code>988b5a0</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/setup-buildx-action/issues/347">#347</a>
      from crazy-max/skip-malformed-context</li>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/2c215620b8bfc319fa4c45228e004e292677fd33"><code>2c21562</code></a>
      chore: update generated content</li>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/3382292cd51ea1cda5852caf2e65d8e7b3f1c2ca"><code>3382292</code></a>
      check for malformed docker context</li>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/3d68780484996aa9d417bb9016193885cdf1f299"><code>3d68780</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/setup-buildx-action/issues/341">#341</a>
      from crazy-max/docker-context-tls</li>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/d069e98648dcd5f11d3f726983a778dcf30aeca0"><code>d069e98</code></a>
      chore: update generated content</li>
      <li><a
      href="https://github.com/docker/setup-buildx-action/commit/8b850f86dc46ba7eb11e02c7d3db66aeb2b0f022"><code>8b850f8</code></a>
      create docker context if default one has TLS data loaded</li>
      <li>See full diff in <a
      href="https://github.com/docker/setup-buildx-action/compare/aa33708b10e362ff993539393ff100fa93ed6a27...988b5a0280414f521da01fcc63a27aeeb4b104db">compare
      view</a></li>
      </ul>
      </details>
      <br />
      
      Updates `docker/build-push-action` from 6.5.0 to 6.7.0
      <details>
      <summary>Release notes</summary>
      <p><em>Sourced from <a
      href="https://github.com/docker/build-push-action/releases">docker/build-push-action's
      releases</a>.</em></p>
      <blockquote>
      <h2>v6.7.0</h2>
      <ul>
      <li>Print info message for build summary support checks by <a
      href="https://github.com/crazy-max"><code>@​crazy-max</code></a> in <a
      href="https://redirect.github.com/docker/build-push-action/pull/1211">docker/build-push-action#1211</a></li>
      </ul>
      <p><strong>Full Changelog</strong>: <a
      href="https://github.com/docker/build-push-action/compare/v6.6.1...v6.7.0">https://github.com/docker/build-push-action/compare/v6.6.1...v6.7.0</a></p>
      <h2>v6.6.1</h2>
      <ul>
      <li>Bump <code>@​docker/actions-toolkit</code> from 0.37.0 to 0.37.1 in
      <a
      href="https://redirect.github.com/docker/build-push-action/pull/1205">docker/build-push-action#1205</a></li>
      </ul>
      <p><strong>Full Changelog</strong>: <a
      href="https://github.com/docker/build-push-action/compare/v6.6.0...v6.6.1">https://github.com/docker/build-push-action/compare/v6.6.0...v6.6.1</a></p>
      <h2>v6.6.0</h2>
      <ul>
      <li>Generate GitHub annotations for <a
      href="https://docs.docker.com/build/checks/">build checks</a> by <a
      href="https://github.com/crazy-max"><code>@​crazy-max</code></a> in <a
      href="https://redirect.github.com/docker/build-push-action/pull/1197">docker/build-push-action#1197</a></li>
      <li>Bump <code>@​docker/actions-toolkit</code> from 0.35.0 to 0.37.0 in
      <a
      href="https://redirect.github.com/docker/build-push-action/pull/1196">docker/build-push-action#1196</a>
      <a
      href="https://redirect.github.com/docker/build-push-action/pull/1198">docker/build-push-action#1198</a></li>
      </ul>
      <p><strong>Full Changelog</strong>: <a
      href="https://github.com/docker/build-push-action/compare/v6.5.0...v6.6.0">https://github.com/docker/build-push-action/compare/v6.5.0...v6.6.0</a></p>
      </blockquote>
      </details>
      <details>
      <summary>Commits</summary>
      <ul>
      <li><a
      href="https://github.com/docker/build-push-action/commit/5cd11c3a4ced054e52742c5fd54dca954e0edd85"><code>5cd11c3</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/build-push-action/issues/1211">#1211</a>
      from crazy-max/summary-info-message</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/0aba704831628413787ada4cf0e8f04d977f1d21"><code>0aba704</code></a>
      chore: update generated content</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/23c657a01f105567f668c7596ce8e5a038da2555"><code>23c657a</code></a>
      print info message for build summary support checks</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/16ebe778df0e7752d2cfcbd924afdbbd89c1a755"><code>16ebe77</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/build-push-action/issues/1205">#1205</a>
      from docker/dependabot/npm_and_yarn/docker/actions-t...</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/646a62b4f2189bfb0b46bfa1676692e7bff6e4d7"><code>646a62b</code></a>
      chore: update generated content</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/d92ab1347f14b597b6d4a546737ec663aef4a184"><code>d92ab13</code></a>
      chore(deps): Bump <code>@​docker/actions-toolkit</code> from 0.37.0 to
      0.37.1</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/4f7cdeb0f05278b464e71357394bf2c61f94138e"><code>4f7cdeb</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/build-push-action/issues/1198">#1198</a>
      from docker/dependabot/npm_and_yarn/docker/actions-t...</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/ad3cd774a4f620adb18ba3ba3fa178c73b624bd2"><code>ad3cd77</code></a>
      chore: update generated content</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/3efbc133663acf954bb07c2ab14201de1e1733a4"><code>3efbc13</code></a>
      chore(deps): Bump <code>@​docker/actions-toolkit</code> from 0.36.0 to
      0.37.0</li>
      <li><a
      href="https://github.com/docker/build-push-action/commit/2dbe91db48e489c125002fbd97678eaf1e0e563e"><code>2dbe91d</code></a>
      Merge pull request <a
      href="https://redirect.github.com/docker/build-push-action/issues/1197">#1197</a>
      from crazy-max/build-checks</li>
      <li>Additional commits viewable in <a
      href="https://github.com/docker/build-push-action/compare/5176d81f87c23d6fc96624dfdbcd9f3830bbe445...5cd11c3a4ced054e52742c5fd54dca954e0edd85">compare
      view</a></li>
      </ul>
      </details>
      <br />
      
      
      Dependabot will resolve any conflicts with this PR as long as you don't
      alter it yourself. You can also trigger a rebase manually by commenting
      `@dependabot rebase`.
      
      [//]: # (dependabot-automerge-start)
      [//]: # (dependabot-automerge-end)
      
      ---
      
      <details>
      <summary>Dependabot commands and options</summary>
      <br />
      
      You can trigger Dependabot actions by commenting on this PR:
      - `@dependabot rebase` will rebase this PR
      - `@dependabot recreate` will recreate this PR, overwriting any edits
      that have been made to it
      - `@dependabot merge` will merge this PR after your CI passes on it
      - `@dependabot squash and merge` will squash and merge this PR after
      your CI passes on it
      - `@dependabot cancel merge` will cancel a previously requested merge
      and block automerging
      - `@dependabot reopen` will reopen this PR if it is closed
      - `@dependabot close` will close this PR and stop Dependabot recreating
      it. You can achieve the same result by closing it manually
      - `@dependabot show <dependency name> ignore conditions` will show all
      of the ignore conditions of the specified dependency
      - `@dependabot ignore <dependency name> major version` will close this
      group update PR and stop Dependabot creating any more for the specific
      dependency's major version (unless you unignore this specific
      dependency's major version or upgrade to it yourself)
      - `@dependabot ignore <dependency name> minor version` will close this
      group update PR and stop Dependabot creating any more for the specific
      dependency's minor version (unless you unignore this specific
      dependency's minor version or upgrade to it yourself)
      - `@dependabot ignore <dependency name>` will close this group update PR
      and stop Dependabot creating any more for the specific dependency
      (unless you unignore this specific dependency or upgrade to it yourself)
      - `@dependabot unignore <dependency name>` will remove all of the ignore
      conditions of the specified dependency
      - `@dependabot unignore <dependency name> <ignore condition>` will
      remove the ignore condition of the specified dependency and ignore
      conditions
      
      
      </details>
      
      Signed-off-by: default avatardependabot[bot] <support@github.com>
      Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    • thiolliere's avatar
      Remove deprecated calls in cumulus-parachain-system (#5439) · f0323d52
      thiolliere authored
      Calls were written to be removed after June 2024. This PR removes them.
      
      This PR will break users using those calls. The call won't be decodable
      by the runtime, so it should fail early with no consequences. The
      functionality must be same as before, users will just need to use the
      calls in `System`.
    • Przemek Rzad's avatar
      Make the PR template a default for new PRs (#5462) · 5a84374f
      Przemek Rzad authored
      A follow-up to https://github.com/paritytech/polkadot-sdk/pull/5447
      
      Instead of having an option to select a PR template (like is the case
      with issues), this change will make the one PR template we have the
      default, it will show up for every new PR.
      
      Also updated one link so it works properly in the PR body.
    • Liu-Cheng Xu's avatar
      Only log the propagating transactions when they are not empty (#5424) · 6ecbde33
      Liu-Cheng Xu authored
      This can make the log cleaner, especially when you specify `--log
      sync=debug`.
  3. Aug 26, 2024
    • Oliver Tale-Yazdi's avatar
      [CI] Fix SemVer check base commit (#5361) · b34d4a08
      Oliver Tale-Yazdi authored
      
      After seeing some cases of reported changes that did not happen by the
      merge request proposer (like
      https://github.com/paritytech/polkadot-sdk/pull/5339), it became clear
      that [this](https://github.com/orgs/community/discussions/59677) is
      probably the issue.
      The base commit of the SemVer check CI is currently using the *latest*
      master commit, instead of the master commit at the time when the MR was
      created.
      
      Trying to get the correct base commit now. For this to be debugged, i
      have to wait until another MR is merged into master.
      
      ---------
      
      Signed-off-by: default avatarOliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
    • Nazar Mokrynskyi's avatar
      Sync status refactoring (#5450) · dd1aaa47
      Nazar Mokrynskyi authored
      
      As I was looking at the coupling between `SyncingEngine`,
      `SyncingStrategy` and individual strategies I noticed a few things that
      were unused, redundant or awkward.
      
      The awkward change comes from
      https://github.com/paritytech/substrate/pull/13700 where
      `num_connected_peers` property was added to `SyncStatus` struct just so
      it can be rendered in the informer. While convenient, the property
      didn't really belong there and was annoyingly set to `0` in some
      strategies and to `num_peers` in others. I have replaced that with a
      property on `SyncingService` that already stored necessary information
      internally.
      
      Also `ExtendedPeerInfo` didn't have a working `Clone` implementation due
      to lack of perfect derive in Rust and while I ended up not using it in
      the refactoring, I included fixed implementation for it in this PR
      anyway.
      
      While these changes are not strictly necessary for
      https://github.com/paritytech/polkadot-sdk/issues/5333, they do reduce
      coupling of syncing engine with syncing strategy, which I thought is a
      good thing.
      
      Reviewing individual commits will be the easiest as usual.
      
      ---------
      
      Co-authored-by: default avatarDmitry Markin <dmitry@markin.tech>
    • Egor_P's avatar
      Add build options to the srtool build step (#4956) · 3cbefaf1
      Egor_P authored
      
      This PR adds possibility to set BUILD_OPTIONS to the "Srtool Build" step
      in the release pipeline while building runtimes.
      
      Colses: https://github.com/paritytech/release-engineering/issues/213
      
      ---------
      
      Co-authored-by: default avatarBastian Köcher <git@kchr.de>
      Co-authored-by: default avatarEgorPopelyaev <EgorPopelyaev@users.noreply.github.com>
    • Muharem Ismailov's avatar
      `MaybeConsideration` extension trait for `Consideration` (#5384) · ad0de749
      Muharem Ismailov authored
      Introduce `MaybeConsideration` extension trait for `Consideration`.
      
      The trait allows for the management of tickets that may represent no
      cost. While the `MaybeConsideration` still requires proper handling, it
      introduces the ability to determine if a ticket represents no cost and
      can be safely forgotten without any side effects.
      
      The new trait is particularly useful when a consumer expects the cost to
      be zero under certain conditions (e.g., when the proposal count is below
      a threshold N) and does not want to store such consideration tickets in
      storage. The extension approach allows us to avoid breaking changes to
      the existing trait and to continue using it as a non-optional version
      for migrating pallets that utilize the `Currency` and `fungible` traits
      for `holds` and `freezes`, without requiring any storage migration.
  4. Aug 25, 2024
    • Lech Głowiak's avatar
      Skip slot before creating inherent data providers during major sync (#5344) · 178e699c
      Lech Głowiak authored
      # Description
      
      Moves `create_inherent_data_provider` after checking if major sync is in
      progress.
      
      ## Integration
      
      Change is internal to sc-consensus-slots. It should be no-op unless
      someone is using fork of this SDK.
      
      ## Review Notes
      
      Motivation for this change is to avoid calling
      `create_inherent_data_providers` if it's result is going to be discarded
      anyway during major sync. This has potential to speed up node operations
      during major sync by not calling possibly expensive
      `create_inherent_data_provider`.
      
      TODO: labels T0-node D0-simple
      TODO: there is no tests for `Slots`, should I add one for this case?
      
      # Checklist
      
      * [x] My PR includes a detailed description as outlined in the
      "Description" and its two subsections above.
      * [x] My PR follows the [labeling requirements](CONTRIBUTING.md#Process)
      of this project (at minimum one label for `T`
        required)
      * External contributors: ask maintainers to put the right label on your
      PR.
      * [ ] I have made corresponding changes to the documentation (if
      applicable)
      * [ ] I have added tests that prove my fix is effective or that my
      feature works (if applicable)
    • Przemek Rzad's avatar
      Add symlinks for code of conduct and contribution guidelines (#5447) · 91b5a49a
      Przemek Rzad authored
      Addresses
      [this](https://github.com/paritytech/eng-automation/issues/10#issuecomment-2286391379).
      
      > Another side note is the checkmarks in
      https://github.com/paritytech/polkadot-sdk/community. It seems like even
      though we have `CONTRIBUTING.md` in `/docs` it is not picked up in this
      list. I am not even sure what is the benefit of following these
      standards, but it is probably for the best to do it.
  5. Aug 24, 2024
  6. Aug 23, 2024
    • Yuri Volkov's avatar
      Moving `Find FAIL-CI` check to GHA (#5377) · b3c2a25b
      Yuri Volkov authored
    • eskimor's avatar
      Remove panic, as proof is invalid. (#5427) · d26d7f1d
      eskimor authored
      
      `validity_vote` function is also called from `import_statement` not only
      from `import_candidate`. The proof still holds if we assume seconded
      statements always come before valid statements, which should be the case
      but is not actually enforced by this module at all. On top of this the
      proof is not local.
      
      Co-authored-by: default avatareskimor <eskimor@no-such-url.com>
    • Nazar Mokrynskyi's avatar
      Reactive syncing metrics (#5410) · 4057ccd7
      Nazar Mokrynskyi authored
      This PR untangles syncing metrics and makes them reactive, the way
      metrics are supposed to be in general.
      
      Syncing metrics were bundled in a way that caused coupling across
      multiple layers: justifications metrics were defined and managed by
      `ChainSync`, but only updated periodically on tick in `SyncingEngine`,
      while actual values were queried from `ExtraRequests`. This convoluted
      architecture was hard to follow when I was looking into
      https://github.com/paritytech/polkadot-sdk/issues/5333.
      
      Now metrics that correspond to each component are owned by that
      component and updated as changes are made instead of on tick every
      1100ms.
      
      This does add some annoying boilerplate that is a bit harder to
      maintain, but it separates metrics more nicely and if someone queries
      them more frequently will give arbitrary resolution. Since metrics
      updates are just atomic operations I do not expect any performance
      impact of these changes.
      
      Will add prdoc if changes look good otherwise.
      
      P.S. I noticed that importing requests (and corresponding metrics) were
      not cleared ever since corresponding code was introduced in
      https://github.com/paritytech/polkadot-sdk/commit/dc41558b#r145518721
      and I left it as is to not change the behavior, but it might be
      something worth fixing.
      
      cc @dmitry-markin
      
      
      
      ---------
      
      Co-authored-by: default avatarDmitry Markin <dmitry@markin.tech>
    • Branislav Kontur's avatar
      [bridges] Prune messages from confirmation tx body, not from the on_idle (#5006) · e4ffba6e
      Branislav Kontur authored
      
      (Please, do not merge until SA, reverted and restored of
      https://github.com/paritytech/polkadot-sdk/pull/4944)
      
      Original PR with more context:
      https://github.com/paritytech/parity-bridges-common/pull/2211
      Relates to:
      https://github.com/paritytech/parity-bridges-common/issues/2210
      
      ## TODO
      
      - [x] fresh weighs for `pallet_bridge_messages`
      - [x] add `try_state` for `pallet_bridge_messages` which checks for
      unpruned messages - relates to the
      [comment](https://github.com/paritytech/parity-bridges-common/pull/2211#issuecomment-1643224831)
      - [x] ~prepare migration, that prunes leftovers, which would be pruned
      eventually from `on_idle` the
      [comment](https://github.com/paritytech/parity-bridges-common/pull/2211#issuecomment-1643224831)~
      can be done also by `set_storage` / `kill_storage` or with
      `OnRuntimeUpgrade` implementatino when `do_try_state_for_outbound_lanes`
      detects problem.
      
      ## Open question
      
      - [ ] Do we really need `oldest_unpruned_nonce` afterwards?
      - after the runtime upgrade and when `do_try_state_for_outbound_lanes`
      pass, we won't need any migrations here
          - we won't even need `do_try_state_for_outbound_lanes`
      - please check comments bellow:
      https://github.com/paritytech/polkadot-sdk/pull/4944#discussion_r1666737961
      
      ---------
      
      Signed-off-by: default avatarBranislav Kontur <bkontur@gmail.com>
      Co-authored-by: default avatarSerban Iorga <serban@parity.io>
      Co-authored-by: default avatarSvyatoslav Nikolsky <svyatonik@gmail.com>
      Co-authored-by: command-bot <>
    • Przemek Rzad's avatar
      Change the chain to Rococo in the parachain template Zombienet config (#5279) · 9fecd898
      Przemek Rzad authored
      
      Following this:
      https://github.com/paritytech/polkadot-sdk-parachain-template/pull/11
      
      ---------
      
      Co-authored-by: default avatarShawn Tabrizi <shawntabrizi@gmail.com>
      Co-authored-by: default avatarBastian Köcher <git@kchr.de>
    • Przemek Rzad's avatar
      Improve the appearance of crates on `crates.io` (#5243) · c66f7bd4
      Przemek Rzad authored
      ## Context
      
      Currently, many crates have no readme files, even though they are public
      and available on crates.io.
      Others have just a couple of words that does not look super presentable.
      
      Even though probably nobody starts a journey with `polkadot-sdk` or its
      documentation with a readme of a random low-level crate, I think it
      would look more mature to have a little better readmes there.
      
      So, in an attempt to improve [the
      aesthetics](https://github.com/paritytech/eng-automation/issues/10) of
      `polkadot-sdk`, I propose a set of consistent, branded, better-looking
      readmes for all published crates.
      
      ## What's inside
      
      - ~~New readme files for published crates.~~
      - A python script to generate new readmes, for the crates that have
      none.
        - It will skip crates that do have a readme, and private crates.
      - Added a new image asset to the repo - logo with a background.
      - The main readme of the repo uses a [nice
      trick](https://github.com/paritytech/polkadot-sdk/blob/ce6938ae/README.md?plain=1#L4-L5)
      to accompany both light and dark modes - but that doesn't work on
      `crates.io` so a single logo with a background is needed.
      
      ## Example
      
      ### Current
      
      ![Screenshot 2024-08-04 at 16 13
      36](https://github.com/user-attachments/assets/3ae0881d-0f40-4614-9d2c-3c95029f0820)
      
      ### Changed
      
      ![Screenshot 2024-08-04 at 16 12
      28](https://github.com/user-attachments/assets/fa7eadc8-aec8-4f77-84d9-54d63ce189cd)
    • Alexander Theißen's avatar
      Add initial version of `pallet_revive` (#5293) · 559fa1db
      Alexander Theißen authored
      This is a heavily modified and stripped down version of
      `pallet_contracts`. We decided to fork instead of extend the old pallet.
      Reasons for that are:
      
      - There is no benefit of supporting both on the same pallet as the
      intended payload for the new pallet (recompiled YUL) will be using a
      different ABI.
      - It is much easier since it allows us to remove all the code that was
      necessary to support Wasm and focus fully on running cross compiled YUL
      contracts.
      
      **The code is reviewable but can't be merged because it depends on an
      unreleased version of PolkaVM via git.**
      
      ## Current state
      
      All tests are passing and the code is not quick and dirty but written to
      last. The work is not finished, though. It is included in the
      `kitchensink-runtime` and a node can be built. However, we merge early
      in order to be able to start testing other components as early as
      possible.
      
      Outstanding changes are tracked here and will be merged separately:
      https://github.com/paritytech/polkadot-sdk/issues/5308
      
      ## Syscall Interface
      
      The syscall interface is best explored by generating the docs of this
      crate and looking at the `SyscallDoc` trait. Arguments are passed in
      registers a0-a5 in the order they are listed. If there are more than 6
      arguments (call, instantiate) a pointer to a packed struct of the
      arguments is expected as the only argument. I plan to create variants of
      those syscalls with less arguments specifically for YUL.
      
      Functions are just referenced by their name as ASCII within the PolkaVM
      container. Rather than by a syscall number as it was the case in the
      last implementation.
       
      
      ## Changes vs. `pallet_contracts`
      
      The changes are too numerous to list them all here. This is an
      incomplete list:
      
      - Use PolkaVM instead of wasmi to execute contracts
      - Made Runtime generic over a new `Memory` trait as we can't map memory
      directly on PolkaVM anymore
      - No static verification on code upload. Everything is a determinstic
      runtime failure
      - Removed all migrations and reset the pallet version
      - Removed the nonce storage item and instead use the deployers account
      nonce to generate a unique trie
      - We now bump the deployers account nonce on contract instantiation to
      they are bumped even within a batch transaction
      - Removed the instantiation nonce host function: We should add a new
      `instantiate` variant as a replacement for thos
      - ContractInfoOf of uses the indentity hasher now
      - Remove the determinism feature: User of that feature should switch to
      soft floats
      - The `unstable` attribute has been replaced by a `api_version`
      attribute to declare at which version an API became available
      	- leaving out that attribute makes the API effectively unstable
      - a new `api_version` field on the CodeInfo makes sure that old
      contracts can't access new APIs (necessary due to lack of static
      verification.
      - Added a `behaviour_version` field to CodeInfo that can used if we need
      to introduce breaking changes and keep the old behaviour for existing
      contracts
      - Unified storage vs. transient and fixed vs. variable sized keys all
      into one set of multiplexing host functions
      - Removed all contract observeable limits from the `Config` trait and
      instead hardcode them
      - Removed the Schedule
      - Removed all deprecated host functions
      - Simplify chain extension as preperation for making it a pre-compile
      
      ---------
      
      Co-authored-by: command-bot <>
    • Gustavo Gonzalez's avatar
      Update OpenZeppelin template documentation (#5398) · 4ffccac4
      Gustavo Gonzalez authored
      
      # Description
      Updates `template.rs` to reflect the two OZ templates available and a
      short description
      
      # Checklist
      
      * [x] My PR includes a detailed description as outlined in the
      "Description" and its two subsections above.
      * [x] My PR follows the [labeling requirements](CONTRIBUTING.md#Process)
      of this project (at minimum one label for `T`
        required)
      * External contributors: ask maintainers to put the right label on your
      PR.
      * [x] I have made corresponding changes to the documentation (if
      applicable)
      
      ---------
      
      Co-authored-by: default avatarKian Paimani <5588131+kianenigma@users.noreply.github.com>
      Co-authored-by: default avatarShawn Tabrizi <shawntabrizi@gmail.com>
    • Nazar Mokrynskyi's avatar
      Remove the need to wait for target block header in warp sync implementation (#5431) · 6d819a61
      Nazar Mokrynskyi authored
      I'm not sure if this is exactly what
      https://github.com/paritytech/polkadot-sdk/issues/3537 meant, but I
      think it should be fine to wait for relay chain before initializing
      parachain node fully, which removed the need for background task and
      extra hacks throughout the stack just to know where warp sync should
      start.
      
      Previously there were both `WarpSyncParams` and `WarpSyncConfig`, but
      there was no longer any point in having two data structures, so I
      simplified it to just `WarpSyncConfig`.
      
      Fixes https://github.com/paritytech/polkadot-sdk/issues/3537
  7. Aug 22, 2024