mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-07-08 18:17:22 +00:00

Files

T

Andrei Sandu 04a9071e2a Use higher priority for PVF preparation in dispute/approval context (#4172 )

Related to https://github.com/paritytech/polkadot-sdk/issues/4126
discussion

Currently all preparations have same priority and this is not ideal in
all cases. This change should improve the finality time in the context
of on-demand parachains and when `ExecutorParams` are updated on-chain
and a rebuild of all artifacts is required. The desired effect is to
speed up approval and dispute PVF executions which require preparation
and delay backing executions which require preparation.

---------

Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>

2024-04-19 08:15:59 +00:00

benches

Set clippy lints in workspace (requires rust 1.74) (#2390 )

2023-12-13 15:11:07 +01:00

common

Align dependencies with parity-bridges-common (#3937 )

2024-04-02 13:41:01 +00:00

execute-worker

PVF: re-preparing artifact on failed runtime construction (#3187 )

2024-02-28 16:29:27 +00:00

prepare-worker

Sync Cargo.toml and crates.io versions (#3034 )

2024-01-26 18:14:03 +00:00

src

Use higher priority for PVF preparation in dispute/approval context (#4172 )

2024-04-19 08:15:59 +00:00

tests/it

Fix spelling mistakes across the whole repository (#3808 )

2024-03-26 13:57:57 +00:00

build.rs

Adapt test worker to profile flag (#2450 )

2023-11-24 12:32:43 +02:00

Cargo.toml

Align dependencies with parity-bridges-common (#3937 )

2024-04-02 13:41:01 +00:00

README.md

refactor pvf security module (#3047 )

2024-02-11 09:59:10 +00:00

README.md

PVF Host

This is the PVF host, responsible for responding to requests from Candidate Validation and spawning worker tasks to fulfill those requests.

Running basic tests

Running cargo test in the pvf/ directory will run unit and integration tests.

Note: some tests run only under Linux, x86-64, and/or with the ci-only-tests feature enabled.

See the general Testing instructions for more information on running tests and observing logs.

Running a test-network with zombienet

Since this crate is consensus-critical, for major changes it is highly recommended to run a test-network. See the "Behavior tests" section of the Testing docs for full instructions.

To run the PVF-specific zombienet test:

RUST_LOG=parachain::pvf=trace zombienet --provider=native spawn zombienet_tests/functional/0001-parachains-pvf.toml

Testing on Linux

Some of the PVF functionality, especially related to security, is Linux-only, and some is x86-64-only. If you touch anything security-related, make sure to test on Linux x86-64! If you're on a Mac, you can either run a VM or you can hire a VPS and use the open-source tool EternalTerminal to connect to it.¹

Unlike ssh, ET preserves your session across disconnects, and unlike another popular persistent shell, mosh, it allows scrollback. ↩︎