mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 20:27:58 +00:00

Files

T

Davide Galassi 4c10fd2a41 Move cryptographic hashing procedures to crypto folder. (#2306 )

Step towards https://github.com/paritytech/polkadot-sdk/issues/1975

As reported
https://github.com/paritytech/polkadot-sdk/issues/1975#issuecomment-1774534225
I'd like to encapsulate crypto related stuff in a dedicated folder.

Currently all cryptographic primitive wrappers are all sparsed in
`substrate/core` which contains "misc core" stuff.

To simplify the process, as the first step with this PR I propose to
move the cryptographic hashing there.

The `substrate/crypto` folder was already created to contains `ec-utils`
crate.

Notes:
- rename `sp-core-hashing` to `sp-crypto-hashing`
- rename `sp-core-hashing-proc-macro` to `sp-crypto-hashing-proc-macro`
- As the crates name is changed I took the freedom to restart fresh from
version 0.1.0 for both crates

---------

Co-authored-by: Robert Hambrock <roberthambrock@gmail.com>

2024-01-22 23:36:14 +00:00

benches

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

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

common

Move cryptographic hashing procedures to crypto folder. (#2306 )

2024-01-22 23:36:14 +00:00

execute-worker

Use clone instead of fork on pvf (#2477 )

2024-01-21 11:15:36 +00:00

prepare-worker

Use clone instead of fork on pvf (#2477 )

2024-01-21 11:15:36 +00:00

src

Make candidate validation bounded again (#2125 )

2024-01-21 13:56:44 +00:00

tests/it

Use clone instead of fork on pvf (#2477 )

2024-01-21 11:15:36 +00:00

build.rs

Adapt test worker to profile flag (#2450 )

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

Cargo.toml

Bump libc from 0.2.149 to 0.2.152 (#2994 )

2024-01-19 15:04:02 +00:00

README.md

PVF: Add test instructions (#2058 )

2023-11-28 14:23:25 +01: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, amd64, 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 amd64-only. If you touch anything security-related, make sure to test on Linux amd64! 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. ↩︎