Skip to content

fix(repo): filter empty optional fields from installed manifest - #475

Merged
akremenetsky merged 1 commit into
masterfrom
hotfix/migration-from-0-2-0
Jul 14, 2026
Merged

fix(repo): filter empty optional fields from installed manifest#475
akremenetsky merged 1 commit into
masterfrom
hotfix/migration-from-0-2-0

Conversation

@akremenetsky

Copy link
Copy Markdown
Member

Empty optional fields (exports: {}, imports: {}, etc.) in the repo element manifest caused constant updates in the universal agent due to a diff between target and actual resources on every iteration.

  • Add MANIFEST_OPTIONAL_FIELDS to InstalledManifest and filter empty values in from_repo_element
  • Simplify _make_installed_manifest to use a loop over the shared MANIFEST_OPTIONAL_FIELDS tuple instead of individual if-blocks
  • Add regression tests for empty and non-empty optional field handling

@akremenetsky
akremenetsky requested a review from a team as a code owner July 13, 2026 17:38

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request refactors manifest generation by introducing a centralized list of optional fields (MANIFEST_OPTIONAL_FIELDS) in InstalledManifest. It updates from_repo_element to filter out empty optional fields, ensuring consistency with _make_installed_manifest and preventing unnecessary diff detections. Additionally, corresponding unit tests have been added to verify this behavior. There are no review comments, and I have no further feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Empty optional fields (exports: {}, imports: {}, etc.) in the repo
element manifest caused constant updates in the universal agent due to
a diff between target and actual resources on every iteration.

- Add MANIFEST_OPTIONAL_FIELDS to InstalledManifest and filter empty
  values in from_repo_element
- Simplify _make_installed_manifest to use a loop over the shared
  MANIFEST_OPTIONAL_FIELDS tuple instead of individual if-blocks
- Add regression tests for empty and non-empty optional field handling

Signed-off-by: Anton Kremenetsky <anton.kremenetsky@gmail.com>
@akremenetsky
akremenetsky force-pushed the hotfix/migration-from-0-2-0 branch from 6b99bd8 to 7921c01 Compare July 13, 2026 18:26

@cassi-volkova cassi-volkova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The manifest normalization itself is consistent in the focused checks, but the newly added persistent-config synchronization has a retryability defect that can leave an upgraded installation with a stale mirror.

Comment thread exordos_core/cmd/bootstrap.py
@akremenetsky
akremenetsky dismissed cassi-volkova’s stale review July 13, 2026 19:21

The review isn't actual

@akremenetsky
akremenetsky merged commit 1277448 into master Jul 14, 2026
7 checks passed
@akremenetsky
akremenetsky deleted the hotfix/migration-from-0-2-0 branch July 14, 2026 08:11
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.

5 participants