inbuxa/inbuxa-server
1
0
Fork 0
Code Issues Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

Tests: retire pending-rebuild, which nothing has been gated behind for a day

Browse Source 
The feature held the shared tests of features the fork hadn't rebuilt yet.
All nine are built and the last gate came off with per-domain directories,
so the feature was defined and documented but gated nothing.

The crate builds and holds the same tests without it: 113 by default, 118
with postgres, mysql and redis. SPEC §2.2b keeps its account of the first
import and now says when the gates came off, so a spec that still describes
a suite as gated reads as the record of its own date, which is what
monitoring.md's gate table already calls itself.
This commit is contained in:
jcoffey-dev
2026-09-19 17:28:14 -07:00
parent 08b3210cff
commit dac1808bbd
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/spec/SPEC.md
+4 -1
View File
@@ -132,7 +132,10 @@ repository. Instead:
default: the OIDC-directory, tenant and archiving suites; the four default: the OIDC-directory, tenant and archiving suites; the four
telemetry suites (alerts, metrics, tracing, webhooks); and the LLM parts of telemetry suites (alerts, metrics, tracing, webhooks); and the LLM parts of
the spam-filter suite. Each gate carries an `inbuxa: pending-rebuild` comment the spam-filter suite. Each gate carries an `inbuxa: pending-rebuild` comment
and comes off when its feature is rebuilt. and comes off when its feature is rebuilt. All nine features were rebuilt by
2026-09-19, so every gate came off and the feature itself was removed from
`tests/Cargo.toml` that day. A spec that still describes a suite as gated is
describing the state at its own date.
- Those gated suites are shared, AGPL test code that exercises Enterprise - Those gated suites are shared, AGPL test code that exercises Enterprise
behavior. That makes them a clean source for the feature specs, and ready-made behavior. That makes them a clean source for the feature specs, and ready-made
acceptance tests for the rebuilds. acceptance tests for the rebuilds.
tests/Cargo.toml
+3 -4
View File
@@ -4,10 +4,9 @@ version = "0.16.22"
edition = "2024" edition = "2024"
[features] [features]
# Tests for Enterprise features the fork hasn't rebuilt yet. Off by default, so # `pending-rebuild` held the shared tests of features the fork hadn't rebuilt
# the crate compiles without them. Each gate is marked `inbuxa: pending-rebuild`, # yet. All nine are built and every gate is off, so the feature went on
# and comes off when its feature's rebuild lands. # 2026-09-19 (docs/spec/SPEC.md §2.2b).
pending-rebuild = []
#default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "nats", "azure", "foundationdb"] #default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "nats", "azure", "foundationdb"]
#default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "foundationdb"] #default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "foundationdb"]
default = ["rocks", "sqlite"] default = ["rocks", "sqlite"]