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

Scheduled reports: a feature byte of their own #162

Merged
jcoffey-dev merged 1 commits from fix/scheduled-reports-own-prefix into main 2026-10-07 06:14:36 +00:00
Conversation 0 Commits 1 Files Changed 2
+150 -3
jcoffey-dev commented 2026-10-07 06:05:20 +00:00
Owner
Copy link
Copy source

2026.10.6.2 kept scheduled reports under S in the fork subspace, which scale-out storage (Sb/Sm/Sl, replica markers Sr+index) and the spam-rules updater (Sr marker, Sf, Sn) already use. Nothing overwritten on prod (checked read-only: only the 2-byte Sr marker and the 10-byte digest key under Sr; key lengths differ), but scans could cross features. Moves to G (unused in code and on prod) with a one-time move of the 2026.10.6.2 records, deleting only those exact keys.

Checked: system test with a legacy digest, legacy settings and the spam marker (moved / moved / untouched), model tests, every fork check, CI locked builds.

2026.10.6.2 kept scheduled reports under **S** in the fork subspace, which scale-out storage (Sb/Sm/Sl, replica markers Sr+index) and the spam-rules updater (Sr marker, Sf, Sn) already use. Nothing overwritten on prod (checked read-only: only the 2-byte Sr marker and the 10-byte digest key under Sr; key lengths differ), but scans could cross features. Moves to **G** (unused in code and on prod) with a one-time move of the 2026.10.6.2 records, deleting only those exact keys. Checked: system test with a legacy digest, legacy settings and the spam marker (moved / moved / untouched), model tests, every fork check, CI locked builds.
jcoffey-dev added 1 commit 2026-10-07 06:05:20 +00:00
Scheduled reports: a feature byte of their own
ci / fork-checks (pull_request) Skipped
Details
ci / build (pull_request) Skipped
Details
github/ci (branch) GitHub Actions
Details
ci / github (pull_request) Successful in 9m6s
Details
3510b28ce1 
2026.10.6.2 kept scheduled reports under S in the fork's subspace, a
byte scale-out storage (Sb, Sm, Sl, replica markers Sr + index) and the
spam-rules updater (the Sr marker, Sf, Sn) already use. Nothing was
overwritten (the keys differ in length), but a scan of Sr + id could
read the others' keys, and one byte per feature is the rule. They move
to G, unused anywhere.

ensure_digest moves what 2026.10.6.2 wrote, once per process: what
reads as a report from the Sr + 8-byte-id range, and the settings at
Ss, deleting only those exact keys. The system test writes a legacy
digest, legacy settings and the spam marker, and checks the first two
moved and the marker didn't.
jcoffey-dev merged commit d7d94904d5 into main 2026-10-07 06:14:36 +00:00
jcoffey-dev deleted branch fix/scheduled-reports-own-prefix 2026-10-07 06:14:36 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 dependencies
Dependency updates
 documentation
Docs, README or site copy
 duplicate
Already tracked elsewhere
 enhancement
New feature or improvement
 good first issue
Good for newcomers
 help wanted
Contributions welcome
 invalid
Not a valid issue
 needs info
Waiting on the reporter for details
 question
Needs an answer, not a code change
 security
Security issue or hardening
 translation
New language or translation fixes
 wontfix
Will not be worked on
priority
p1
High priority
priority
p2
Medium priority
priority
p3
Low priority
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcoffey-dev (John Coffey)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#162