Skip to content
Snippets Groups Projects
  1. Dec 09, 2024
    • Alexandru Gheorghe's avatar
      Fix `Possible bug: Vote import failed` after aggression is enabled (#6690) · e22a0ef6
      Alexandru Gheorghe authored
      
      After finality started lagging on kusama around 025-11-25 15:55:40
      validators started seeing ocassionally this log, when importing votes
      covering more than one assignment.
      ```
      Possible bug: Vote import failed
      ```
      
      That happens because the assumption that assignments from the same
      validator would have the same required routing doesn't hold after you
      enabled aggression, so you might end up receiving the first assignment
      then you modify the routing for it in `enable_aggression` then your
      receive the second assignment and the vote covering both assignments, so
      the rouing for the first and second assingment wouldn't match and we
      would fail to import the vote.
      
      From the logs I've seen, I don't think this is the reason the network
      didn't fully recover until the failsafe kicked it, because the votes had
      been already imported in approval-voting before this error.
      
      ---------
      
      Signed-off-by: default avatarAlexandru Gheorghe <alexandru.gheorghe@parity.io>
      (cherry picked from commit da953454)
      e22a0ef6
    • EgorPopelyaev's avatar
      Update Cargo.lock · ed1932e2
      EgorPopelyaev authored
      ed1932e2
    • Morgan Adamiec's avatar
      Apply plan · 9c8ad9bd
      Morgan Adamiec authored
      9c8ad9bd
  2. Dec 04, 2024
  3. Dec 03, 2024
  4. Nov 27, 2024
  5. Nov 21, 2024
  6. Nov 13, 2024
    • Egor_P's avatar
      [Release|CI/CD] Fix audiences changelog template (#6444) · b5eb098d
      Egor_P authored
      This PR addresses an issue mentioned
      [here](https://github.com/paritytech/polkadot-sdk/issues/6424#issuecomment-2467042441).
      The problem was that when the prdoc file has two audiences, but only one
      description like in
      [prdoc_5660](https://github.com/paritytech/polkadot-sdk/blob/master/prdoc/1.16.0/pr_5660.prdoc)
      it was ignored by the template.
      b5eb098d
  7. Nov 12, 2024
  8. Nov 07, 2024
  9. Nov 05, 2024
  10. Oct 25, 2024
  11. Oct 17, 2024
  12. Oct 15, 2024
  13. Oct 11, 2024
    • Egor_P's avatar
      [stable2407] Backport docker fix to 2407 (#6017) · 88c32501
      Egor_P authored
      This PR backports fixes for the docker publishing flow from master:
      - https://github.com/paritytech/polkadot-sdk/pull/5896
      - https://github.com/paritytech/polkadot-sdk/pull/5387
      88c32501
  14. Oct 10, 2024
  15. Oct 09, 2024
  16. Oct 08, 2024
  17. Oct 07, 2024
  18. Sep 19, 2024
  19. Sep 17, 2024
  20. Sep 16, 2024
  21. Sep 10, 2024
  22. Sep 09, 2024
  23. Sep 05, 2024
    • github-actions[bot]'s avatar
      [stable2407] Backport #5581 (#5603) · c28ec0fb
      github-actions[bot] authored
      Backport #5581 into `stable2407` (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>
      c28ec0fb