Veza Project: TODO Triage & Cleanup

Date: 2025-12-07 Status: Post-Remediation Check

1. Stream Server (Rust)

🔴 Critical: Offline Compilation Blocked

Issue: veza-stream-server fails to compile with cargo check due to missing sqlx-data.json or live database connection. Error: error communicating with database: Connection refused (os error 111) Location: usage of sqlx::query! macros in:

src/core/encoding_pool.rs
src/core/encoding_service.rs Remediation:
Short term: Ensure PostgreSQL is running and accessible via DATABASE_URL during development.
Long term: Generate sqlx-data.json using cargo sqlx prepare and commit it to the repository to allow offline compilation.

🟡 Tech Debt: Unused Variables

There are multiple warnings for unused variables in veza-stream-server:

stream_server/src/error.rs: unused variable: err
stream_server/src/streaming/hls.rs: unused variable: quality Action: Review logic to see if these variables should be used or prefixed with _.

2. Chat Server (Rust)

🟡 Tech Debt: Unused Imports (Cleaned up)

The chat server compiles successfully, but has several warnings for unused imports and variables that should be cleaned up in a future maintenance pass:

src/main.rs: unused import: sqlx::PgPool, unused futures_util imports.
src/event_bus.rs: unused fields config and connection in RabbitMQEventBus.
src/config.rs: unused imports. Action: Run cargo fix --bin "chat-server" and cargo fix --lib -p chat_server to automatically remove most of these.

3. Backend (Go)

🟡 Testing Gap

veza-backend-api/internal/handlers/room_handler_test.go contains disabled tests or tests marked with TODO(P2). Action: Re-enable and fix these tests to ensure regression coverage for room management.

4. Documentation

REPORT_STATUS_2025_12_06.md refers to the pre-fix state.
POST_REMEDIATION_REPORT.md tracks the progress of the remediation. Action: Keep POST_REMEDIATION_REPORT.md updated as the single source of truth for current status.

2.1 KiB Raw Blame History