What problem does it solve?
Developers working on Materialize need to know the correct commands and pitfalls for compiling, running, formatting, and linting the codebase, including non-obvious issues like shared CockroachDB state and multi-crate constructor updates.
Core Features & Use Cases
- Compilation checks: Use
cargo check and bin/environmentd --build-only instead of cargo build or cargo run, and verify mz-sqllogictest compiles when changing mz_environmentd::Config.
- Local execution: Start Materialize with
bin/environmentd --optimized, connect via psql on ports 6875 or 6877, and safely handle --reset against the shared CockroachDB metadata backend.
- Formatting and linting: Run
bin/fmt, bin/lint, and cargo clippy --all-targets -- -D warnings to keep the tree clean.
- Use Case: You added a field to
mz_environmentd::Config and CI fails mysteriously. The skill explains that cargo check -p mz-environmentd misses the sqllogictest constructor, so you must run cargo check -p mz-sqllogictest --all-targets.
Quick Start
Ask the assistant to start Materialize locally and check that my changes compile across all affected crates.