Support / bug reports (testing)

What to include in a report

Every report should contain the following:

Version: git commit hash (or tag), OS/kernel.
Launch config: config (angarabase.conf) and launch command.
Reproduction steps: SQL/steps/client (psql/ORM/tool).
Expected vs actual behavior: what was expected and what happened.
Artifacts:
- Server logs.
- If this is a crash/recovery/backup topic: summary.json and the entire artifacts/ folder.

Helpful tooling (already in repo)

Nightly-style evidence pack

Running a local evidence pack (single run):

tools/ci/nightly_gate.sh --runs 1 --root artifacts/nightly_local

Diagnostics bundle

Collecting a diagnostic bundle:

tools/diagnostics_bundle/run.sh --root artifacts/diagnostics_bundle

Specific scenarios

Hang / stall

If the problem is a hang or stall:

Attach client-side timeout/hang description.
Attach server logs.
Attach stack trace or diag bundle (if possible).
Check known issues — specifically KI-2026-001 (pg_database probe stall).

Crash / recovery

Attach summary.json from artifacts/.
Attach the full artifacts/ directory.
Specify whether this occurred during normal startup, restart, or backup/restore.

Unexpected SQLSTATE

Provide the full error text (SQLSTATE code + message).
Check known issues — many SQLSTATE codes are documented as expected behavior.

What’s Next

Known Issues and SQLSTATE — check if your problem is described as a known limitation.
Client Compatibility — if the problem is in the driver or client.
Diagnostics — how to collect an EXPLAIN, slow-log, or sys.* snapshot to attach to an issue.