Skip to content

No labels!

There aren’t any labels for this repository quite yet.

446 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
O-sentry
O-sentry
Originated from an in-the-wild panic report.
91
O-sqlsmith
O-sqlsmith
1
O-sre
O-sre
For issues SRE opened or otherwise cares about tracking.
33
O-support
O-support
Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs
279
O-testcluster
O-testcluster
Issues found or occurred on a test cluster, i.e. a long-running internal cluster
114
observability-escalation-follow-up
observability-escalation-follow-up
P-0
P-0
Issues/test failures with a fix SLA of 2 weeks
1
P-1
P-1
Issues/test failures with a fix SLA of 1 month
200
P-2
P-2
Issues/test failures with a fix SLA of 3 months
241
P-3
P-3
Issues/test failures with no fix SLA
582
performance-regression-expected
performance-regression-expected
Performance regression is expected in this change
quality-friday
quality-friday
A good issue to work on on Quality Friday
45
regression
regression
Regression from a release.
11
release-blocker
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
85
S-0-corruption-or-data-loss
S-0-corruption-or-data-loss
Unrecoverable corruption, data loss, or other catastrophic issues that can’t be fixed by upgrading.
1
S-0-visible-logical-error
S-0-visible-logical-error
Database stores inconsistent data in some cases, or queries return invalid results silently.
1
S-0
S-0
Extreme impact: many users impacted and irrecoverable outages / data loss
S-1-blocking-adoption
S-1-blocking-adoption
S-1-stability
S-1-stability
Severe stability issues that can be fixed by upgrading, but usually don’t resolve by restarting
3
S-1
S-1
High impact: many users impacted, serious risk of high unavailability or data loss
1
S-2-temp-unavailability
S-2-temp-unavailability
Temp crashes or other availability problems. Can be worked around or resolved by restarting.
6
S-2
S-2
Medium-high impact: many users impacted, risks of availability and difficult-to-fix data errors
7
S-3-erroneous-edge-case
S-3-erroneous-edge-case
Database produces or stores erroneous data without visible error/warning, in rare edge cases.
21
S-3-productivity
S-3-productivity
Severe issues that impede the productivity of CockroachDB developers.
18
S-3-ux-surprise
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
45
S-3-wrong-metadata
S-3-wrong-metadata
Issues causing erroneous metadata or monitoring stats to be returned.
S-3
S-3
Medium-low impact: incurs increased costs for some users (incl lower avail, recoverable bad data)
20
skipped-test
skipped-test
24
stability-period
stability-period
Intended to be worked on during a stability period. Use with the Milestone field to specify version.
14
stability-period-v22.2
stability-period-v22.2
3