llm-kernel 0.29.0

Foundation library for Rust AI-native apps — provider catalog, LLM client, MCP server, search, telemetry, and safety
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

//! TLS crypto provider bootstrap for the `rustls-ring` feature.
//!
//! reqwest 0.13's `rustls-no-provider` feature compiles no crypto provider
//! into the binary and panics at `Client` build time unless a process-default
//! provider is installed first. The `rustls-ring` feature relies on that
//! escape hatch (see #93), so every HTTP client construction site calls
//! [`ensure_tls_provider`] first. The install is idempotent: an already
//! installed provider (e.g. the application's own choice) wins, and the
//! `Err` from the redundant install is ignored.

/// Only compiled when a reqwest-backed feature is active — otherwise the
/// no-op body would trip `dead_code` under `-D warnings`. Without
/// `rustls-ring` this is a no-op: the `rustls-aws-lc-rs` (default) path ships
/// the aws-lc-rs provider inside reqwest and needs no runtime install.
#[cfg(any(
    feature = "client-async",
    feature = "discovery-async",
    feature = "elastic"
))]
pub(crate) fn ensure_tls_provider() {
    #[cfg(feature = "rustls-ring")]
    let _ = rustls::crypto::ring::default_provider().install_default();
}

#[cfg(all(test, feature = "rustls-ring", feature = "client-async"))]
mod tests {
    use super::ensure_tls_provider;

    /// Regression test for the #93 panic path: under `rustls-no-provider`,
    /// building a client without an installed provider panics inside reqwest.
    /// llm-kernel must install the ring provider first.
    #[test]
    fn client_builds_with_ring_provider() {
        ensure_tls_provider();
        let client = reqwest::Client::builder().build();
        assert!(
            client.is_ok(),
            "reqwest client must build after ring provider install"
        );
    }
}