1. Jan 10, 2023
    • Marcin S.'s avatar
      Replace async-std with tokio in PVF subsystem (#6419) · 44fd9566
      Marcin S. authored
      
      
      * Replace async-std with tokio in PVF subsystem
      
      * Rework workers to use `select!` instead of a mutex
      
      The improvement in code readability is more important than the thread overhead.
      
      * Remove unnecessary `fuse`
      
      * Add explanation for `expect()`
      
      * Update node/core/pvf/src/worker_common.rs
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Update node/core/pvf/src/worker_common.rs
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Address some review comments
      
      * Shutdown tokio runtime
      
      * Run cargo fmt
      
      * Add a small note about retries
      
      * Fix up merge
      
      * Rework `cpu_time_monitor_loop` to return when other thread finishes
      
      * Add error string to PrepareError::IoErr variant
      
      * Log when artifacts fail to prepare
      
      * Fix `cpu_time_monitor_loop`; fix test
      
      * Fix text
      
      * Fix a couple of potential minor data races.
      
      First data race was due to logging in the CPU monitor thread even if the
      job (other thread) finished. It can technically finish before or after the log.
      
      Maybe best would be to move this log to the `select!`s, where we are guaranteed
      to have chosen the timed-out branch, although there would be a bit of
      duplication.
      
      Also, it was possible for this thread to complete before we executed
      `finished_tx.send` in the other thread, which would trigger an error as the
      receiver has already been dropped. And right now, such a spurious error from
      `send` would be returned even if the job otherwise succeeded.
      
      * Update Cargo.lock
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      44fd9566
  2. Jan 09, 2023
  3. Jan 07, 2023
    • Tsvetomir Dimitrov's avatar
      disputes pallet: Remove spam slots (#6345) · ed9a1a40
      Tsvetomir Dimitrov authored
      
      
      * disputes pallet: Filter disputes with votes less than supermajority threshold
      
      * Remove `max_spam_slots` usages
      
      * Remove `SpamSlots`
      
      * Remove `SpamSlotChange`
      
      * Remove `Error<T>::PotentialSpam` and stale comments
      
      * `create_disputes_with_no_spam` -> `create_disputes`
      
      * Make tests compile - wip commit
      
      * Rework `test_dispute_timeout`. Rename `update_spam_slots` to `filter_dispute_set`
      
      * Remove `dispute_statement_becoming_onesided_due_to_spamslots_is_accepted` and `filter_correctly_accounts_spam_slots` -> they bring no value with removed spam slots
      
      * Fix `test_provide_multi_dispute_success_and_other`
      
      * Remove an old comment
      
      * Remove spam slots from tests - clean todo comments
      
      * Remove test - `test_decrement_spam`
      
      * todo comments
      
      * Update TODO comments
      
      * Extract `test_unconfirmed_are_ignored` as separate test case
      
      * Remove dead code
      
      * Fix `test_unconfirmed_are_ignored`
      
      * Remove dead code in `filter_dispute_data`
      
      * Fix weights (related to commit "Remove `SpamSlots`")
      
      * Disputes migration - first try
      
      * Remove `dispute_max_spam_slots` + storage migration
      
      * Fix `HostConfig` migration tests
      
      * Deprecate `SpamSlots`
      
      * Code review feedback
      
      * add weight for storage version update
      * fix bound for clear()
      
      * Fix weights in disputes migration
      
      * Revert "Deprecate `SpamSlots`"
      
      This reverts commit 8c4d967c7b061abd76ba8b551223918c0b9e6370.
      
      * Make mod migration public
      
      * Remove `SpamSlots` from disputes pallet and use `storage_alias` in the migration
      
      * Fix call to `clear()` for `SpamSlots` in migration
      
      * Update migration and add a `try-runtime` test
      
      * Add `pre_upgrade` `try-runtime` test
      
      * Fix some test names in `HostConfiguration` migration
      
      * Link spamslots migration in all runtimes
      
      * Add `test_unconfirmed_disputes_cause_block_import_error`
      
      * Update guide
      
      - Remove `SpamSlots` related information from roadmap/implementers-guide/src/runtime/disputes.md
      - Add 'Disputes filtering' to Runtime section of the Implementor's guide
      
      * Update runtime/parachains/src/configuration/migration.rs
      
      Co-authored-by: default avatarMarcin S. <[email protected]>
      
      * Code review feedback - update logs
      
      * Code review feedback: fix weights
      
      * Update runtime/parachains/src/disputes.rs
      
      Co-authored-by: default avatars0me0ne-unkn0wn <[email protected]>
      
      * Additional logs in disputes migration
      
      * Fix merge conflicts
      
      * Add version checks in try-runtime tests
      
      * Fix a compilation warning`
      
      Co-authored-by: default avatarMarcin S. <[email protected]>
      Co-authored-by: default avatars0me0ne-unkn0wn <[email protected]>
      ed9a1a40
  4. Jan 06, 2023
  5. Jan 05, 2023
  6. Jan 04, 2023
  7. Jan 03, 2023
  8. Jan 02, 2023
    • Michal Kucharczyk's avatar
      BlockId removal: refactor: BlockBackend::block|block_status (#6477) · 01fcc274
      Michal Kucharczyk authored
      * BlockId removal: refactor: BlockBackend::block|block_status
      
      It changes the arguments of:
      -  `BlockBackend::block`
      -  `BlockBackend::block_status`
      
      method from: `BlockId<Block>` to: `Block::Hash`
      
      This PR is part of BlockId::Number refactoring analysis (paritytech/substrate#11292)
      
      * update lockfile for {"substrate"}
      
      * ".git/.scripts/fmt.sh"
      
      Co-authored-by: parity-processbot <>
      01fcc274
  9. Dec 30, 2022
    • Bradley Olson's avatar
      Update dispute participation on active leaves update (#6303) · 539a9a91
      Bradley Olson authored
      
      
      * Passed candidate events from scraper to participation
      
      * First draft PR 5875
      
      * Added support for timestamp in changes
      
      * Some necessary refactoring
      
      * Removed SessionIndex from unconfirmed_disputes key
      
      * Removed duplicate logic in import statements
      
      * Replaced queue_participation call with re-prio
      
      * Simplifying refactor. Backed were already handled
      
      * Removed unneeded spam slots logic
      
      * Implementers guide edits
      
      * Undid the spam slots refactor
      
      * Added comments and implementers guide edit
      
      * Added test for participation upon backing
      
      * Round of fixes + ran fmt
      
      * Round of changes + fmt
      
      * Error handling draft
      
      * Changed errors to bubble up from reprioritization
      
      * Starting to construct new test
      
      * Clarifying participation function rename
      
      * Reprio test draft
      
      * Very rough bump to priority queue test draft
      
      * Improving logging
      
      * Most concise reproduction of error on third import
      
      * Add `handle_approval_vote_request`
      
      * Removing reprioritization on included event test
      
      * Removing unneeded test config
      
      * cargo fmt
      
      * Test works
      
      * Fixing final nits
      
      * Tweaks to test Tsveto figured out
      
      Co-authored-by: default avatareskimor <[email protected]>
      Co-authored-by: default avatarTsvetomir Dimitrov <[email protected]>
      539a9a91
  10. Dec 27, 2022
  11. Dec 26, 2022
  12. Dec 23, 2022
  13. Dec 22, 2022
  14. Dec 21, 2022
  15. Dec 20, 2022
    • Alexander Samusev's avatar
      [ci] New try-runtime command (#6445) · 87f9e4e1
      Alexander Samusev authored
      
      
      * [ci] New try-runtime command
      
      * restart pipeline
      
      * build features
      
      * fix --features flag
      
      * rm --execution flag
      
      * remove --no-spec-check-panic flag
      
      * change target dir
      
      * debug ccargo target dir
      
      * return target
      
      * try different location for runtime wasm
      
      * build only the runtime crate
      
      * check all generated .wasm files
      
      * adjust paths again
      
      * remove debug command
      
      Co-authored-by: default avatarjoao-paulo-parity <[email protected]>
      87f9e4e1
    • Marcin S.'s avatar
      PVF preparation: do not conflate errors (#6384) · e0a0475a
      Marcin S. authored
      * PVF preparation: do not conflate errors
      
      + Adds some more granularity to the prepare errors.
      + Better distinguish whether errors occur on the host side or the worker.
      + Do not kill the worker if the error happened on the host side.
      + Do not retry preparation if the error was `Panic`.
      + Removes unnecessary indirection with `Selected` type.
      
      * Add missing docs, resolve TODOs
      
      * Address review comments and remove TODOs
      
      * Fix error in CI
      
      * Undo unnecessary change
      
      * Update couple of comments
      
      * Don't return error for stream shutdown
      
      * Update node/core/pvf/src/worker_common.rs
      e0a0475a
    • Michal Kucharczyk's avatar
      BlockId removal: refactor: HeaderBackend::header (#6418) · fcc26d42
      Michal Kucharczyk authored
      * BlockId removal: refactor: HeaderBackend::header
      
      It changes the arguments of:
      - `HeaderBackend::header`,
      - `Client::header`
      
      methods from: `BlockId<Block>` to: `Block::Hash`
      
      This PR is part of BlockId::Number refactoring analysis (paritytech/substrate#11292)
      
      * missed fixes
      
      * BlockId removal: refactor: HeaderBackend::expect_header
      
      It changes the arguments of `HeaderBackend::expect_header` method from: `BlockId<Block>` to: `Block::Hash`
      
      * update lockfile for {"substrate"}
      
      * misspell fixed
      
      Co-authored-by: parity-processbot <>
      fcc26d42
    • Bastian Köcher's avatar
      Update Substrate (#6457) · f687ab00
      Bastian Köcher authored
      f687ab00
  16. Dec 19, 2022
  17. Dec 17, 2022
    • Bastian Köcher's avatar
      Adding some more logs (#6455) · b5e44b70
      Bastian Köcher authored
      * Adding some more logs
      
      More logs are always better! Joke aside, these logs help to debug
      certain issues.
      
      * Apply suggestions from code review
      b5e44b70
  18. Dec 16, 2022
  19. Dec 15, 2022