Skip to main content

Crate hyprstream

Crate hyprstream 

Source
Expand description

Hyprstream binary - ML inference server

This binary provides the main entry point for the Hyprstream service.

EnumsΒ§

NativeAnnouncementRefreshCompletion πŸ”’
The only native-announcement refresh path used by the production publisher.
ProofReplayStoreSelection πŸ”’
Install the v16 proof admission substrate: the rotating server challenge and the replay admission store (Β§4.6, Β§4.7).
QuicCheckpointPolicy πŸ”’
The only startup policy that consumes PDS lifecycle classification.
TelemetryProvider πŸ”’
Telemetry provider type

ConstantsΒ§

POLICY_INITIAL_PUBLICATION_BUDGET πŸ”’
Policy must serve authority probes while Discovery starts, but is not READY until Discovery accepts its announcement. Only typed pre-dispatch Iroh unavailability can keep that initial publication pending.
POLICY_INITIAL_PUBLICATION_RETRY πŸ”’

FunctionsΒ§

build_cli πŸ”’
Build the CLI using clap builder API with hybrid derive-based subcommands.
dedicated_service_process_name πŸ”’
Process termination is safe only when this process hosts one known service.
flat_key_policy_resolver_credential πŸ”’
The enrolled credential a process-global resolver presents when the process has no selected service identity (a multi-service foreground graph or a plain CLI command). On a flat-key deployment policy resolves to the node root/CA key (#759), so that key IS the policy identity: the resolver may present policy’s enrolled JWT. Without it, cross-process Discovery resolution from such a process goes out anonymous and dies at the MAC dispatch PEP (NoClearance) on labeled nodes. Split-key deployments are unchanged: key mismatch or a missing credential yields None.
foreground_service_process_names πŸ”’
Resolve the services hosted by this foreground process independently of transport profile. Background start commands do not host their children.
handle_quick_command πŸ”’
Handle all quick subcommands β€” orchestrated multi-step workflows.
init_telemetry πŸ”’
Initialize OpenTelemetry with the specified provider
install_envelope_verify_config πŸ”’
Install the process-global envelope verify configuration (#152, #160).
install_process_production_resolver πŸ”’
Install the process production resolver and return whether the authenticated trust source was the OS-owned bootstrap (true) or a DID-anchored source (false). The caller retains this selection so the QUIC startup gate can scope first-boot deferral to the OS-owned path only.
install_proof_admission πŸ”’
install_session_pq_overlay πŸ”’
Install the session PQ binding overlay, the runtime anchoring path for clients no operator can pre-enroll (browsers and other device-generated identities).
load_config πŸ”’
Load HyprConfig from file path or default locations
load_process_signing_key πŸ”’
Required service startup consumes the provisioner’s retained key. Missing or malformed material is never a reason to generate a new identity or use the CLI/root key. Compatibility commands retain their existing key behavior.
main πŸ”’
native_announcement_bearer πŸ”’
Use the current authority projection’s service JWT for envelope identity.
native_service_process_name πŸ”’
Select the process identity before constructing any resolver/client. Transport flags do not decide whose identity a required-native split service uses.
process_identity_name πŸ”’
The identity a foreground process installs into the process-global Discovery resolver and later uses for service startup. A native (iroh-required) selection takes precedence; otherwise a dedicated single-service compatibility process uses its provisioned service identity so the resolver client and the service share one key and enrolled credential. Plain CLI commands get neither.
publish_native_announcement_attempt πŸ”’
The required first result covers both fresh-authority projection and the Discovery publication. An authority error must not bypass the handshake.
quic_checkpoint_policy πŸ”’
refresh_native_announcement πŸ”’
resolve_moq_relay_reach πŸ”’
Resolve a service’s verifying key via the global trust store.
resolve_service_vk πŸ”’
select_iroh_moql_admission_proof πŸ”’
Quinn’s CONNECT path has no process-global MoQL proof slot. Defer proof collection itself to an enabled Iroh profile so Quinn-only multi-service startup does not inherit Iroh’s one-service dialer restriction.
select_proof_replay_store πŸ”’
select_single_process_moql_admission_proof πŸ”’
A QUIC process currently owns one native MoQ dialer and its admission-proof slot. Sharing that slot across separately checkpointed services would make a later service dial as the first service’s DID. Refuse that topology until the dialer is service-scoped; checkpointed services must run separately.
spawn_native_announcement_loop πŸ”’
Spawn the native-announcement refresh loop on its own current-thread Tokio runtime and return a channel for the first announcement result.
start_native_announcement_publisher πŸ”’
Production publisher startup boundary: only required Iroh waits for a successful first publication. Compatibility keeps its retry task alive.
supports_tui πŸ”’
wait_for_policy_initial_publication πŸ”’
with_runtime πŸ”’
Execute a command with the appropriate runtime configuration

Type AliasesΒ§

NativeAnnouncementFirstResult πŸ”’
One-shot sender for the first native-announcement result.
NativeAnnouncementFirstTx πŸ”’
Optional one-shot channel passed to the native-announcement loop body so it can report the result of the first announcement.