Skip to content

fix(mister): avoid no-op frontend.toml rewrites - #379

Merged
wizzomafizzo merged 1 commit into
mainfrom
fix/325-noop-config-writes
Aug 18, 2026
Merged

fix(mister): avoid no-op frontend.toml rewrites#379
wizzomafizzo merged 1 commit into
mainfrom
fix/325-noop-config-writes

Conversation

@wizzomafizzo

Copy link
Copy Markdown
Member

Summary

  • skip frontend.toml serialization and atomic replacement when parsed configuration is unchanged
  • preserve real-change durability with file and parent-directory syncs
  • cover all config save helpers, normalization, metadata preservation, temp-file avoidance, and TOML NaN equality
  • isolate Hub navigation tests from asynchronous warm-restore and persisted focus state

Tests

  • just test
  • just lint

Closes #325

@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 14 minutes

Limit details: You’ve used all 2 included reviews currently available under your plan. You completed 85 included PR reviews in the past 7 days; at that activity level, included reviews refill at 2 reviews per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dcbad060-a541-4f85-923a-8ffaf6ceefd0

📥 Commits

Reviewing files that changed from the base of the PR and between e8512dc and 105c8b5.

📒 Files selected for processing (2)
  • rust/zaparoo-core/src/config.rs
  • tests/ui/tst_navigation.qml

Comment @coderabbitai help to get the list of available commands.

@wizzomafizzo
wizzomafizzo merged commit a0a6cb2 into main Aug 18, 2026
6 checks passed
@wizzomafizzo
wizzomafizzo deleted the fix/325-noop-config-writes branch August 18, 2026 08:06
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.

fix(mister): avoid no-op frontend.toml rewrites

1 participant