* upgrade primitives to allow changing validation function
* set up storage schema for old parachains code
* fix compilation errors
* fix test compilation
* add some tests for past code meta
* most of the runtime logic for code upgrades
* implement old-code pruning
* add a couple tests
* clean up remaining TODOs
* add a whole bunch of tests for runtime functionality
* remove unused function
* fix runtime compilation
* extract some primitives to parachain crate
* add validation-code upgrades to validation params and result
* extend validation params with code upgrade fields
* provide maximums to validation params
* port test-parachains
* add a code-upgrader test-parachain and tests
* fix collator tests
* move test-parachains to own folder to work around compilation errors
* fix test compilation
* update the Cargo.lock
* fix parachains tests
* remove dbg! invocation
* use new pool in code-upgrader
* bump lockfile
* link TODO to issue
* Ensure that table router is always build
This pr ensures that the table router is always build, aka the future is
resolved. This is important, as the table router internally spawns tasks
to handle gossip messages. Handling gossip messages is not only required
on parachain validators, but also on relay chain validators to receive collations.
Tests are added to ensure that the assumptions hold.
* Fix compilation
* Switch to closures
* Remove empty line
* Revert "Remove empty line"
This reverts commit 0d4aaba1780aec1c8d61e1d5dcf7768918af02d9.
* Revert "Switch to closures"
This reverts commit d128c4ecc02c911552a3bfd2142b5a4f7b1338ba.
* Hybrid approach
* Rename test
* Make trait crate local
* Companion PR to splitting Roles
* Fix network tests
* Fix service build
* Even more fixing
* Oops, quick fix
* use is_network_authority in grandpa service config
Co-authored-by: André Silva <andre.beat@gmail.com>
* add dummy parachains.toml
* flesh out parachains.toml
* finish phase-1 rendering
* render to svg instead
* put graphviz svg through sanitizer so github can render
* return to PNG
Up to now consensus instances used the main channel to communicate with
the background network worker. This lead to a race condition when
sending a local collation and dropping the router before driving the
send local collation future until it is finished. This pr changes the
communication between worker and the instances to use their own
channels. This has the advantage that we don't need an extra
`DropConsensusNetworking` message as the network is dropped
automatically when the last sender is dropped.
* add pov-block gossip message to network
* tests for pov-block gossip
* integrate pov-block gossip into main protocol
* message validation fetches pov blocks
* remove stray dbg! invocation
* test that pov-block is fetched from relay-parent topic
* Use `add_benchmark` macro
* Return error if `batches` is empty
* Update Cargo.lock
* Companion for #5463 (#953)
* Fix test with genesis block 0
* Update Cargo.lock
* Adds a SigningContext type
* Bump spec versions
* Fixes requested changes
* Bump ParachainHost api_version and guard signing_context call
* Improve error message
* If there is no signing_context api use default value
Co-authored-by: Robert Habermeier <rphmeier@gmail.com>
* Parachains double vote handler initial implementation.
* Make tests test the actual slashing.
* Implement SignedExtension validation of double vote reports.
* Fixes build after merge
* Review fixes
* Adds historical session proofs
* Review fixes.
* Bump runtime spec_version
* Get the session number from the proof
* Check that proof matches session
* Change signature type on DoubleVoteReport
* Adds docs and removes blank lines
* Removes leftover code
* Fix build
* Fix build after a merge
* Apply suggestions from code review
Co-Authored-By: Robert Habermeier <rphmeier@gmail.com>
* Prune ParentToSessionIndex
* Remove a clone and a warning
Co-authored-by: Robert Habermeier <rphmeier@gmail.com>
Co-authored-by: Gavin Wood <gavin@parity.io>
* Updates for the new democracy
* Introduce progressive democracy
Also move to "master" branch of Substrate ready for continuous
sync with Substrate master.
* Move publish_draft_release to test stage
Also remove the alert_pending_release job since it's no longer needed
* delete alert_pending_release.sh
* Add splitting substrate changes into subsections
Kian Paimani