The public issue tracker for ScramDB, the programmable distributed hyperscale UTAP SQL database. The engine is developed privately; bugs, feature requests, documentation problems and performance reports live here, in the open.
Open an issue, or jump straight to the form you need:
| Form | For | |
|---|---|---|
| 🐛 | Bug report | Something is broken or wrong |
| ✨ | Feature request | Something ScramDB cannot do yet |
| 📖 | Documentation issue | A page is wrong, missing, or unclear |
| 🐌 | Performance problem | Slower or heavier than it should be |
Every form is short, and almost every field is optional. Bugs and performance reports ask for three: what happened, your version, and how you run ScramDB. Nothing else is required.
Do not polish it. A rough report filed today is worth more than a perfect one you never send, and we will ask if we need more. Duplicates are fine too: search first if you like, but we would rather see it twice than not at all.
- Version. Run
SELECT version();and paste the line, or name the build you installed (v1.0.3, or asha-<short>prerelease from releases). - How you run it. Installed binary, Docker container, or Kubernetes with the Helm chart.
- The smallest repro you have. A few lines of SQL beats a description of the SQL. If you cannot isolate one, file it anyway and say so.
Please keep credentials and private data out of logs and queries. A redacted snippet, or an id we can ask you about, is enough.
| Instead of an issue | Go here |
|---|---|
| A question, setup help, or "is this even a bug?" | Discord |
| How something is supposed to work | Documentation |
| A security vulnerability | Report it privately, never as a public issue |
Every new issue starts as status/needs-triage. A maintainer then adds an
area/ label for the part of ScramDB involved, adds a severity/ label if it
is a bug or a performance report, and either reproduces it
(status/confirmed) or asks you for one more detail (status/needs-info).
Fixes ship through releases:
sha-<short> prereleases are published continuously, and vX.Y.Z tags are the
promoted stable builds.
| Namespace | Means | Set by |
|---|---|---|
type/ |
what the issue is: bug, feature, docs, perf, question |
the form you pick |
area/ |
the part of ScramDB it touches: query-engine, storage, cluster, vector-anode, semantic-ai, wire-protocol, udf-packages, backup-pitr, kubernetes, docker, cli, observability, licensing |
triage |
status/ |
where it stands: needs-triage, needs-info, confirmed, in-progress, blocked |
triage |
severity/ |
how much it hurts: critical, high, medium, low |
triage |
The full set with colors and descriptions lives in
.github/labels.yml. To apply it to this repository
(creates what is missing, updates what exists, deletes nothing):
./.github/scripts/sync-labels.sh