Build Errors

Check that all submodules (duckdb, cucascade, extension-ci-tools, substrait, duckdb-python) are at expected commits. If any show a + prefix (out of sync), warn the user and offer:

git submodule update --init --recursive

b. Pixi environment: Verify running inside pixi. If not, remind user to run pixi shell first.

c. sccache health:

sccache --show-stats

If it hangs or returns an error, restart:

sccache --stop-server && sccache --start-server

Error Analysis Strategy

When analyzing build errors:

1. Read the full error -- don't just look at the first line. Template errors and linker errors often have the root cause buried in later lines.
2. Check the error file -- read the source file at the error location to understand context.
3. Check recent changes -- git diff HEAD~1 to see if the error was introduced by a recent change.
4. Look for cascading errors -- fix the first error first; subsequent errors may be caused by it.
5. CUDA-specific: Check GPU architecture compatibility, CUDA standard version, and separable compilation settings.

Common Patterns

See error-patterns.md in this directory for a catalog of known Sirius build errors and their fixes.

Important Notes

• Most effective when errors are localized and fixes are 1-4 lines
• Always present each fix as a draft for review before applying (in interactive mode)
• Track which files were modified so changes can be reverted
• If a clean build is needed, suggest rm -rf build but confirm with user first (destructive)
• Reduce parallelism if OOM during build: CMAKE_BUILD_PARALLEL_LEVEL=4 make