pola-rs/polars · error

this tool requires the `dsl-schema` feature

Error message

this tool requires the `dsl-schema` feature

What it means

Panic in the dsl-schema binary: it was built without the dsl-schema cargo feature, so the schema-generation implementation is compiled out and running it always fails. Rebuild polars-plan with --features dsl-schema.

Source

Thrown at crates/polars-plan/src/bin/dsl-schema.rs:22

//! `dsl-schema [generate|update-hashes|check-hashes] [PATH]`
//! - `generate` the DSL schema as a full JSON file in the current directory
//! - `update-hashes` stored in the schema hashes file,
//! - `check-hashes` in the schema hashes file against the hashes from the code.
//!
//! The generated schema is affected by active features. To use a complete schema, first build
//! the whole workspace with all features:
//! ```sh
//! cargo build --all-features
//! ./target/debug/dsl-schema update-hashes
//! ./target/debug/dsl-schema check-hashes
//!
//! The tool has the code schema built-in. After code changes, you need to run
//! `cargo build --all-features` again.
//! ```

fn main() {
    #[cfg(not(feature = "dsl-schema"))]
    panic!("this tool requires the `dsl-schema` feature");

    #[cfg(feature = "dsl-schema")]
    {
        impls::run();
    }
}

#[cfg(feature = "dsl-schema")]
mod impls {
    use std::fs::File;
    use std::io::Write;
    use std::path::Path;

    use polars_plan::dsl::DslPlan;
    use schemars::Schema;
    use sha2::Digest;

    const DEFAULT_HASHES_PATH: &str = "crates/polars-plan/dsl-schema-hashes.json";

View on GitHub (pinned to 9b5d73fd00)

Solutions

1. Build the dsl-schema tool with the `dsl-schema` cargo feature enabled.
2. Run the schema maintenance via the project's Makefile/CI target that enables the feature.

When it happens

Trigger: This panic/expect fires when execution reaches an unguarded state described by: "this tool requires the `dsl-schema` feature". Typical triggers: unsupported dtype or feature-gated code path reached at runtime, invalid user input or environment variable value, calling API methods in the wrong order or on mismatched types, or data (lengths, offsets, ranges) violating the function's preconditions.

Common situations: Encountered when input data or configuration does not meet the preconditions of the throwing code path ("this tool requires the `dsl-schema` feature"). Common cases: missing Cargo feature flags, mismatched dtypes/lengths between arrays or series, out-of-range temporal values, malformed environment variables, or operations on unsupported/complex nested types.

AI-assisted analysis of pola-rs/polars@9b5d73fd00 (2026-08-19). Data as JSON: /api/errors/c0018fe7a8ed8347. Report an issue: GitHub.