Skip to content
Snippets Groups Projects
  1. Oct 01, 2024
  2. Sep 26, 2024
  3. Sep 25, 2024
  4. Sep 24, 2024
  5. Sep 20, 2024
  6. Sep 19, 2024
  7. Sep 18, 2024
  8. Sep 17, 2024
  9. Sep 16, 2024
  10. Sep 13, 2024
  11. Sep 12, 2024
  12. Sep 09, 2024
  13. Sep 06, 2024
  14. Sep 05, 2024
    • github-actions[bot]'s avatar
      [stable2409] Backport #5581 (#5604) · 1c6da61f
      github-actions[bot] authored
      Backport #5581 into `stable2409` (cc @franciscoaguirre
      
      ).
      
      The dry-run shows in `forwarded_xcms` all the messages in the queues
      at the time of calling the API.
      Each time the API is called, the result could be different.
      You could get messages even if you dry-run something that doesn't send
      a message, like a `System::remark`.
      
      This commit fixes this by clearing the message queues before doing the
      dry-run, so the only messages left are the ones the users of the API actually
      care about.
      
      Co-authored-by: default avatarFrancisco Aguirre <franciscoaguirreperez@gmail.com>
  15. Sep 04, 2024
    • EgorPopelyaev's avatar
      Move prdoc to release folder · 935c04e1
      EgorPopelyaev authored
    • Alexandru Vasile's avatar
      [backport] chainHead/fix: Report bestBlock events only for newBlock reports (#5527) (#5582) · 533b9511
      Alexandru Vasile authored
      This backports original PR:
      https://github.com/paritytech/polkadot-sdk/pull/5527 to the release
      branch
      
      
      ```
      
      The https://github.com/paritytech/polkadot-sdk/issues/5512 has surfaced that we reported a `BestBlock` event for a block not previously reported via `NewBlock`.
      
      This is because of a race between:
      - the stream of events that announces new blocks
      - `self.client.info().best_block`
      
      It is possible that `client.info()` contains newer information than the information polled from the block stream (that may be lagging).
      
      To mitigate this, instead of relying on the client's info use the last finalized block to emit a new event.
      
      There are two cases when a new best block event is emitted:
      - The best block is in the pruned list and is reported immediately
      - The best block is not a descendant of the last finalized block 
      
      Closes: https://github.com/paritytech/polkadot-sdk/issues/5512 
      
      Thanks @jsdw and @josepot for helping debug this :pray:
      
       
      
      cc @paritytech/subxt-team
      ```
      
      Signed-off-by: default avatarAlexandru Vasile <alexandru.vasile@parity.io>
      Co-authored-by: default avatarSebastian Kunert <skunert49@gmail.com>
  16. Sep 03, 2024