Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 15 additions & 6 deletions quest/m0/ci/mbx-r2-verify.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,11 @@ nightly.yml --branch main --event schedule`), never a dispatch on a branch.

## Plan

Decided 2026-11-07 (maintainer, /quest-unblock): agents collect the R2
numbers with this desktop's wrangler login, and the maintainer only picks the
lifecycle. Baseline that day: 720,249 objects / 1.2 TB, with 18,006,968
`GetObject` and 4,892,769 `PutObject` requests from 2026-10-16 to 2026-11-07.
Comment on lines +29 to +30

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These counts do not reconcile with the object count on their face: under the 30-day expiry every write from 2026-10-16 onward is still live on 2026-11-07, so 4.9M successful PutObject calls would mean 4.9M objects unless most overwrote existing keys or were refused (1.2 TB / 720,249 is ~1.67 MB per object, which fits the object count). Since the maintainer picks the lifecycle from these numbers, could you record the exact query and confirm the counts are scoped to mbx-moq-dev?

Technical details
# Baseline request counts may not be bucket-scoped

## Affected sites
- `quest/m0/ci/mbx-r2-verify.md:29-30` — records 4,892,769 `PutObject` beside 720,249 live objects under a 30-day expiry.
- `quest/m0/ci/mbx-r2-verify.md:143-146` — prescribes the `r2OperationsAdaptiveGroups` query without its scope.

## Required outcome
- The request counts are reproducible and demonstrably scoped to `mbx-moq-dev`, or annotated with what they include (refused/failed PUTs, retries, sampling, or account-wide totals).

## Suggested approach (optional)
- Re-run the query with `filter: { bucketName: "mbx-moq-dev" }` and `sum { requests }` grouped by `actionType`, and paste the query next to the numbers.

## Open questions for the human (optional)
- Does `requests` include 4xx responses, such as a read-only job's refused writes? No write in this window can have expired yet.


Decided 2026-11-05 (maintainer, /quest-audit): ✅ the release pull request
check moved to [m3](/quest/m3/mbx-r2-release-cache.md) (m2 before the milestone re-cut) behind the cut, since
`release` gets the platform Rust cache only when the cut merges `main` into
Expand Down Expand Up @@ -132,12 +137,16 @@ feature unification, so changed compiler inputs remain a separate cause.
reuse, restore-plus-build comparison and rebuild-frequency evidence in the
Goal. Current timings are not a matched-commit comparison, and macOS's
inherited-prediction misses remain unexplained.
- Maintainer: from about 2026-11-26, collect R2 bucket size and request counts
for the first month and check that the six old oversized manifests expired.
R2's account metrics need the maintainer's Cloudflare login, which agents
lack. Then decide the lifecycle in `infra/mbx/lifecycle.json`: shorten,
keep or lengthen the 30 days. Recommended: keep 30 days unless storage cost
or the rebuild count argues otherwise.
- moq-dev/moq: no earlier than 2026-11-26, an agent on the maintainer's
desktop collects `mbx-moq-dev`'s size and request counts for the first
month and checks that the six old oversized manifests expired. Size comes
from `npx wrangler r2 bucket info mbx-moq-dev`. Request counts come from
Cloudflare's GraphQL API (`r2OperationsAdaptiveGroups`, filtered on
`bucketName` and grouped by `actionType`), authenticated with the
`oauth_token` in `~/.config/.wrangler/config/default.toml`. Then put the
lifecycle in `infra/mbx/lifecycle.json` to the maintainer, with the numbers:
shorten, keep or lengthen the 30 days. Recommended: keep 30 days unless
storage cost or the rebuild count argues otherwise.

## Related

Expand Down