starlark-dev

Debug Kurtosis Starlark packages by inserting print() statements within .star files to inspect execution state and isolate logic errors. This print-based debugging technique helps trace variables during the plan-based execution model without requiring external debuggers.

The plan-based execution model in Starlark separates package execution into distinct planning and execution phases. Developers define instructions during the planning phase, which the engine then executes deterministically, enabling local verification of complex multi-container environments before deployment.

Create and test Kurtosis Starlark packages locally by authoring .star files and running a local example package to observe phase interactions. Iterate package development using local verification to ensure deterministic task execution before deployment.

A Kurtosis Starlark package is used to define and orchestrate multi-container test environments programmatically. Developers author .star files to automate environment setup, enabling deterministic local testing and verification of distributed systems without manual Docker configuration.

Kurtosis Starlark does not support standard Python debuggers; it relies on print-based debugging within .star files. Developers insert print() statements to trace execution flow and inspect variables during the plan-based execution model for troubleshooting package logic.

Kurtosis Starlark packages may fail to execute correctly due to logic errors in the planning phase or invalid service definitions in .star files. Use print-based debugging to trace execution flow and verify local package behavior before deployment.