Repository navigation
fix(id-world): manifest plan leaves omitted grants/ceiling/schedules/profile alone (#817) - #858
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 41 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2304a97986
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| // Profile: the all-default profile inherits the server on every field, | ||
| // so it is how a manifest says nothing about the profile — leave the | ||
| // live profile alone. A present profile replaces when it differs. | ||
| if desired.profile != WorldExecutionProfile::default() && desired.profile != current.profile { |
There was a problem hiding this comment.
Distinguish an explicitly empty profile from an omitted profile
When a world already has profile overrides, an explicit profile = {} or empty [profile] table now produces no SetProfile step, so users can no longer reset those overrides to server inheritance through the manifest. WorldExecutionProfile defines all-None fields as inheriting server limits, and the existing apply_steps handler supports applying that default profile. Track profile presence separately, as with grants and schedules, so omission leaves the live state alone while an explicitly empty profile still clears overrides.
Useful? React with 👍 / 👎.
|
Verification correction (2026-10-25 sweep): the PR body says '17/17 PASS' for the world_manifest suite — the correct count is 11/11. Re-ran on the exact PR head 2304a97 after the main merge: |
|
Sweep merge: the nix flake check leg was CANCELLED at the 60-minute id-check cap (run 40176026710, started 08:17Z, cancelled 09:17Z) — the #551 flake-cap infra pattern, not a failure of this change; run/treefmt/Nix flake evaluation/CodeRabbit all SUCCESS. Change re-verified locally this run on head 2304a97: |
Fixes #817
plan()inpkgs/id/src/world_manifest.rstreated omitted manifest fields as authoritative: a minimal manifest revoked every grant, widened the ceiling to the whole catalog (the security-sensitive direction), cancelled every schedule, and replaced the live profile — contradicting the struct doc's 'empty fields are left alone, so a minimal manifest drifts nothing'.Change (world_manifest.rs only):
grantsandschedulesbecomeOption<..>: omitted = leave the live state alone; present — even empty (grants = [],schedules = {}) — is authoritative and clears/reconciles exactly.ceiling: an omitted ceiling (Nonein the manifest) now leaves the live ceiling alone, so a manifest that never mentions the ceiling can never widen it. A present list replaces when it differs. (InWorldState/SetCeiling,Nonestill means the whole catalog.)profile: the all-default profile is how a manifest says nothing about the profile, soplan()leaves the live profile alone in that case.diff()rendering split intorender_steps():SetCeiling { None }(whole catalog) andSetCeiling { Some([]) }(none allowed) now render distinctly —[*] (whole catalog)vs[].Tests: the misleading second half of
an_empty_manifest_drifts_nothingis corrected (a default manifest now drifts nothing against a fully populated state), plus new regressions: a minimal module-only manifest produces only the module step; explicitly-empty fields are authoritative; ceiling None/empty render distinctly. Verified locally: cargo test --no-default-features --features world --lib world_manifest — 17/17 PASS, both on the original base and after merging current main (2304a97); rustfmt clean.Need help on this PR? Tag
@codesmith-botwith what you need.