Some checks failed
audit / audit (push) Has been skipped
ci-cd / build (push) Has been skipped
ci / build (push) Has been skipped
autofix / fix (push) Has been skipped
python-tests / test (push) Failing after 18s
python-tests / test-specific (push) Has been skipped
security-scanning / audit (push) Has been skipped
test / test (push) Has been skipped
ci-cd / deploy (push) Has been skipped
ci / deploy (push) Has been skipped
YAML INDENTATION FIX: Use single-line Python commands to avoid indentation Issue: - IndentationError persists due to YAML multi-line string handling - Multi-line Python strings in YAML cause indentation conflicts - Workflow still failing with syntax errors Solution: - Use single-line Python commands with exec() - Escape newlines with \n in exec() strings - Separate commands for each import test - Avoid YAML multi-line string indentation issues Changes: - Single-line venv/bin/python -c commands - exec() with escaped newlines for try/except blocks - Separate commands for src and aitbc imports - Maintains debugging functionality without YAML conflicts Expected results: - No more IndentationError - Import debugging should work - Workflow should continue to pytest execution - Clear feedback on import success/failure This should finally resolve the YAML/Python indentation conflict and allow the workflow to proceed to actual test execution.