* HRMP message ingestion
* Plumb hrmp_watermark to build_collation
* Plumb hrmp_watermark to ValidationResult
* Plumb hrmp outbound messages
* Implement message-broker part of HRMP
* Kill UPWARD_MESSAGES as well
Otherwise, they will get resent each block
* Add sudo versions for easier testing
* Remove the xcmp module
Not useful for the moment
* Doc for HRMP message handler
* Estimate the weight upper bound for on_finalize
* Remove a redundant type annotation
* fix spelling of a method
* Apply suggestions from code review
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* Deabbreviate dmp and hrmp in the message ingestion type
* Don't use binary_search since it's broken by a following rotate
Instead use the linear search. We can afford linear search here since
due to limited scalability of HRMP we can only have at most a couple of
dozens of channels.
* Fix the watermark
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* prevent bond_extra to cause staking actve lower than ed
* prevent bond_extra to cause staking actve lower than ed
* Check in post conditions.
* check rebond as well.
* also change withdraw_unbonded.
* Fix build
* change check format.
* Apply suggestions from code review
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* session_info: use proper timeout in test
* Revert "fix off-by-one error"
This reverts commit 35cb56305a19134acd8a8f881f3aabf999a09d74.
* session_info: use correct EarliestStoredSession when introduced on a live chain
* use saturating_sub
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* session_info: revert the timeout test
* session_info: rust is dumb
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* remove low information density error doc comments
* another round of error dancing
* fix compilation
* remove stale `None` argument
* adjust test, minor slip in command
* only add AvailabilityError for full node features
* another None where none shuld be
* Update weights for polkadot
* add Kusama weights
* add westend weights
* remove claims weight files
claims still uses in-line weights which is fine cause it is a polkadot specific pallet
Co-authored-by: Parity Benchmarking Bot <admin@parity.io>
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* *: Update to libp2p v0.32.0
* Cargo.lock: Update async-tls to 0.10.2
* client/network/request_response: Adjust to new request response events
* client/network/request_response.rs: Clean up silently failing responses
* client/network/discovery: Lazily instantiate mdns
* client/network/discovery: Exclude MdnsWrapper for target_os unknown
* client/network/discovery: Fix indentation
* client/network/request-response: Use LruCache to track pending resp time
* client/network/request_responses: Fix early connection closed error
* client/network/request-response: Replace debug_assert with debug
* client/network/request-response: Fix typo
* client/network/request-response: Don't emit event on send_response fail
* client/network/request-response: Revert waker.wake_by_ref()
* client/network/request-resp: Make duration in InboundRequest optional
* client/network/req-resp: Don't emit two events for busy builder
When a response builder is busy incoming requests are dropped.
Previously this was reported both via a `ResponseFailure::Busy` and a
`ReponseFailure::Network(InboundFailure::Omisssion)` event.
With this commit the former is removed, leaving only the latter in
place.
* update to latest master
* updates on docs, license, meta
* hide ssrs behind feature flag
* implement remaining functions on the server
* sign server line length fix
* fix tests
* fixup in-memory-keystore
* adding failsafe
* skipping ecdsa test for now
* remote keystore param
* remote sign urls made available
* integrating keystore remotes features
* don't forget the dependency
* remove old cruft
* reset local keystore
* applying suggestions
* Switch to single remote, minor grumbles
* minor grumbles, docs
* Allow Backend::for_keys_in_child_storage to be aborted by the closure
* Ext::kill_child_storage now takes an upper limit for backend deletion
* Add Storage::storage_kill_limited() runtime interface
* review: Use a new version of kill_storage instead of a new interface
* review: Simplify boolean expression
Co-authored-by: cheme <emericchevalier.pro@gmail.com>
* review: Rename for_keys_in_child_storage
Co-authored-by: cheme <emericchevalier.pro@gmail.com>
* CI: pin md link checker's version to the previous release
* CI: add a whitelist for allowed GH actions pins
* CI: try master tip [skip ci]
* CI: return to a previous markdown-link-check dependency version [skip ci]
* CI: substitute %20 for a literal space [skip ci]
* CI: substitute %20 for a literal space
* Adds consistency checks for the `HostConfiguration`
Besides that it fixes the chain specs to make the consistency checks happy.
* Update runtime/parachains/src/configuration.rs
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Review feedback and test fixes etc
* Update
* More
* I'm an idiot
* Fix tests...
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Do not spam when we can not send a message to a job
There are legal reasons why a job ended. If a job failed, the error is
logged. So, we don't need to log an error when we can not send a message
to a job.
* Review feedback
* Rework `ConnectionsRequests`
Instead of implementing the `Stream` trait, this struct now provides a
function `next()`. This enables us to encode into the type system that
it will always return a value or block indefinitely.
* Review feedback
RK