Skip to content

test(server): guard the bucket boot warning against repeating - #512

Merged
BryanFRD merged 1 commit into
mainfrom
test/boot-log-bucket
Oct 3, 2026
Merged

BryanFRD merged 1 commit into
mainfrom
test/boot-log-bucket

Conversation

@BryanFRD

@BryanFRD BryanFRD commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Refs #510

Review nit on #511: boot_log.rs only covered the access warning on a volume. This adds a bucket config and asserts "objects and locks are stored in a bucket" is logged once across store and app. It fails on the code before #511 (2 occurrences) and passes now.

@BryanFRD
BryanFRD enabled auto-merge (squash) October 3, 2026 07:56

@ferrfleet ferrfleet Bot left a comment

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.

No findings. announce_storage runs only from app(), so the count of 1 holds now. If someone moves the warning into backends, store() and app() would each emit it and the test fails, which is the regression it is meant to catch. Leaving out reclaim is fine: it goes through backends too, so adding it would cover nothing extra and would only make a network round trip to port 9.

@BryanFRD
BryanFRD merged commit 436746d into main Oct 3, 2026
27 checks passed
@BryanFRD
BryanFRD deleted the test/boot-log-bucket branch October 3, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant