Skip to content

Regenerate settings_gen.rs - #19640

Merged
MikhailKasimov merged 1 commit into
masterfrom
bot/regenerate-settings-gen
Oct 9, 2026
Merged

MikhailKasimov merged 1 commit into
masterfrom
bot/regenerate-settings-gen

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

sensor/src/settings_gen.rs is a checked-in mirror of core/settings.py and
data/ua.txt. One of those changed without it being regenerated, so the sensor gate is
refusing master until this lands.

This is generated content - the diff is whatever sensor/tools/gen_settings.py produces
from the current inputs, and the workflow refuses to open a PR that touches any other
file.

Verified in the job that produced this branch (a PR opened by GITHUB_TOKEN does not
trigger workflows, so this PR shows no checks of its own):

  • python3 sensor/tools/gen_settings.py --check
  • cargo fmt --manifest-path sensor/Cargo.toml -- --check
  • cargo test --manifest-path sensor/Cargo.toml --test generated

Editing data/ua.txt from the web UI cannot run the generator, which is why this exists.

core/settings.py or data/ua.txt changed without the checked-in Rust mirror being
regenerated, so the sensor gate refuses the tree. Regenerated by the workflow that
watches those inputs.

Verified in the job that produced it: gen_settings.py --check, cargo fmt --check, and
the generated-constants parity test all pass on this content.
@github-actions
github-actions Bot requested a review from stamparm as a code owner October 9, 2026 14:18
@MikhailKasimov
MikhailKasimov merged commit d445df7 into master Oct 9, 2026
17 checks passed
@MikhailKasimov
MikhailKasimov deleted the bot/regenerate-settings-gen branch October 9, 2026 14:49
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