Skip to content

Fix the fuzzing module, and check feature-gated code in CI - #8

Merged
BhaveshThapar merged 1 commit into
mainfrom
fuzzing-feature-compiles
Aug 24, 2026
Merged

BhaveshThapar merged 1 commit into
mainfrom
fuzzing-feature-compiles

Conversation

@BhaveshThapar

Copy link
Copy Markdown
Owner

The bug

fuzzing::replay_wal and fuzzing::open_sstable still called the pre-seam signatures and had not compiled since #3 landed.

Why nobody noticed

Nothing built with the feature on. cargo clippy --all-targets and cargo test both use default features, and fuzzing is not one.

The actual repair

The two-line fix is not the interesting part. This adds a CI workflow — the repository had none — that runs fmt, clippy --all-targets --all-features -D warnings, and cargo test --all-features.

--all-features because feature-gated code is precisely the code nobody compiles by accident, and a module that has not compiled in four commits is not a module anyone is fuzzing.

`fuzzing::replay_wal` and `fuzzing::open_sstable` still called the pre-seam
signatures and had not compiled since the filesystem seam landed. Nobody
noticed because nothing built with the feature on: `cargo clippy --all-targets`
and `cargo test` both use default features, and `fuzzing` is not one.

So the fix is two lines and the actual repair is the CI file. It runs clippy and
the test suite with `--all-features`, because feature-gated code is precisely
the code nobody compiles by accident, and a module that has not compiled in four
commits is not a module anyone is fuzzing.
@BhaveshThapar
BhaveshThapar merged commit 7cfa882 into main Aug 24, 2026
1 check failed
@BhaveshThapar
BhaveshThapar deleted the fuzzing-feature-compiles branch August 24, 2026 01:34
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