-
orchestra
Generate an orchestra of subsystems from a single struct
-
wdi
interacting with the Windows Driver Installer subsystem
-
tosub
A subsystem lifecycle management library for tokio applications
-
reifydb-sub-tracing
Tracing subsystem for ReifyDB using tracing_subscriber
-
hide_console_ng
Hide console on windows for runtime multi-subsystem applications
-
reifydb-sub-server
Common infrastructure for HTTP and WebSocket server subsystems
-
reifydb-sub-api
Subsystem API and interfaces for ReifyDB
-
re_types_blueprint
The core traits and types that power Rerun's Blueprint sub-system
-
aeth-window
The window subsystem for aeth-rs
-
ktracepoint
implementing tracepoints in operating systems
-
reifydb-sub-logging
High-performance logging subsystem for ReifyDB
-
nu-errors
Core error subsystem for Nushell
-
reifydb-sub-server-http
HTTP server subsystem for ReifyDB using Axum
-
reifydb-sub-worker
Worker pool subsystem for task scheduling and execution
-
nysa
A bus for passing messages around between independent subsystems of an application
-
pezkuwi-node-core-candidate-validation
Pezkuwi crate that implements the Candidate Validation subsystem. Handles requests to validate candidates according to a PVF.
-
pezkuwi-node-core-dispute-coordinator
The node-side components that participate in disputes
-
pezkuwi-collator-protocol
Pezkuwi Collator Protocol subsystem. Allows collators and validators to talk to each other.
-
pezkuwi-statement-distribution
Statement Distribution Subsystem
-
pezkuwi-node-core-prospective-teyrchains
The Prospective Teyrchains subsystem. Tracks and handles prospective teyrchain fragments.
-
pezkuwi-node-core-pvf-checker
Pezkuwi crate that implements the PVF pre-checking subsystem. Responsible for checking and voting for PVFs that are pending approval.
-
pezkuwi-node-core-runtime-api
Wrapper around the teyrchain-related runtime APIs
-
pezkuwi-node-core-chain-selection
Chain Selection Subsystem
-
pezkuwi-node-collation-generation
Collator-side subsystem that handles incoming candidate submissions from the teyrchain
-
pezkuwi-dispute-distribution
Pezkuwi Dispute Distribution subsystem, which ensures all concerned validators are aware of a dispute and have the relevant votes
-
rcommunity
Subsystem for building a community on top of existing business
-
pezkuwi-node-core-approval-voting
Approval Voting Subsystem of the Pezkuwi node
-
kaspa-notify
Kaspa notification subsystem
-
pezkuwi-availability-recovery
The Availability Recovery subsystem. Handles requests for recovering the availability data of included candidates.
-
pezkuwi-node-core-av-store
The Availability Store subsystem. Wrapper over the DB that stores availability data and chunks.
-
pezkuwi-network-bridge
The Network Bridge Subsystem — protocol multiplexer for Pezkuwi
-
pezkuwi-approval-distribution
Pezkuwi Approval Distribution subsystem for the distribution of assignments and approvals for approval checks on candidates over the network
-
pezkuwi-availability-distribution
The Availability Distribution subsystem. Requests the required availability data. Also distributes availability data and chunks to requesters.
-
pezkuwi-node-core-chain-api
The Chain API subsystem provides access to chain related utility functions like block number to hash conversions
-
reifydb-sub-admin
Admin subsystem for web-based administration
-
pezkuwi-node-subsystem
Subsystem traits and message definitions and the generated overseer
-
pezkuwi-gossip-support
Pezkuwi Gossip Support subsystem. Responsible for keeping track of session changes and issuing a connection request to the relevant validators on every new session.
-
mei
Cargo build subsystem
-
pezkuwi-node-core-approval-voting-parallel
Approval Voting Subsystem running approval work in parallel
-
pezkuwi-overseer
System overseer of the Pezkuwi node
-
pezkuwi-node-core-bitfield-signing
Bitfield signing subsystem for the Pezkuwi node
-
pezkuwi-node-metrics
Subsystem metric helpers
-
linux-input
Rust bindings to Linux's input subsystems
Try searching with DuckDuckGo.