Skip to content

fix(adk): skip unmaterializable transport objects - #168

Merged
ThePlenkov merged 3 commits into
mainfrom
fix/skip-unmaterializable-objects
Aug 12, 2026
Merged

fix(adk): skip unmaterializable transport objects#168
ThePlenkov merged 3 commits into
mainfrom
fix/skip-unmaterializable-objects

Conversation

@ThePlenkov

@ThePlenkov ThePlenkov commented Aug 12, 2026

Copy link
Copy Markdown
Member

User description

Summary

Classify OBJECT_METADATA_LOAD_FAILED as unsupported, so a transport can continue materializing exact source components when one object has no usable ADT metadata.

This directly fixes the failure shape in Booking ACR job 15849947781: PROG/ZI_FX_PST_CNTRL_CLS with OBJECT_METADATA_LOAD_FAILED.

Verification

  • ADK tests: 192 passed.
  • adt-flow tests: 26 passed.
  • ADK and adt-flow typechecks: passed.
  • ADK build: passed.
  • Targeted formatting and git diff checks: passed.

Summary by cubic

Treat ADT metadata-load failures as unsupported so checkout skips those objects and continues materializing exact components. Applies to adk manifest building and adt-flow application component filtering.

  • Bug Fixes
    • adk: manifest now classifies object metadata load errors as unsupported, skipping unmaterializable objects without reading source or changing paths.
    • adt-flow: during application component filtering, skip objects with metadata-load failures without reloading metadata; if loadObject throws an AdtFlowError, record them as skipped instead of failing checkout.

Written for commit dabd37e. Summary will update on new commits.

Review in cubic


CodeAnt-AI Description

Allow transport checkout to continue when an object's ADT metadata cannot be loaded

What Changed

  • Objects whose ADT metadata cannot be loaded are treated as unsupported instead of failed
  • Checkout skips those objects without reading their source or changing repository paths
  • Remaining exact source components in the same transport continue through checkout

Impact

✅ Fewer transport checkout failures
✅ Exact components continue despite unusable object metadata
✅ No repository changes for skipped objects

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Classify an object whose ADT metadata cannot be loaded as unsupported, allowing exact components in the same transport to continue through ACR checkout.
@codeant-ai

codeant-ai Bot commented Aug 12, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 31bd06a Aug 12, 2026 · 08:02 08:05

@codeant-ai

codeant-ai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@netlify

netlify Bot commented Aug 12, 2026

Copy link
Copy Markdown

Deploy Preview for adt-cli canceled.

Name Link
🔨 Latest commit dabd37e
🔍 Latest deploy log https://app.netlify.com/projects/adt-cli/deploys/6a7c2c1a0168040008c5bba3

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@ThePlenkov, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: 4b7a6cfe-7f0a-41e3-89d6-3dc480d9eb87

📥 Commits

Reviewing files that changed from the base of the PR and between a69455f and dabd37e.

📒 Files selected for processing (6)
  • openspec/changes/add-adt-flow-transport-checkout/design.md
  • openspec/changes/add-adt-flow-transport-checkout/specs/adt-flow-transport-checkout/spec.md
  • packages/adk/src/transport-source-manifest.ts
  • packages/adk/tests/transport-source-manifest.test.ts
  • packages/adt-flow/src/service.ts
  • packages/adt-flow/tests/service.test.ts

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.

❤️ Share

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

@baz-reviewer

baz-reviewer Bot commented Aug 12, 2026

Copy link
Copy Markdown

Merger

Needs Review

Filtered checkouts still retry loadObject for unsupported entries, so OBJECT_METADATA_LOAD_FAILED aborts checkout instead of being skipped. This is a diff-confirmed correctness blocker with no author response or fix.

Commit 7a6e330 · Evaluated 2026-08-12 08:10 UTC

Review this PR on Baz | Customize your next review

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Aug 12, 2026

@amazon-q-developer amazon-q-developer 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.

Summary

This PR correctly addresses the issue where OBJECT_METADATA_LOAD_FAILED errors were blocking transport materialization. The changes properly classify these errors as unsupported rather than failed, allowing transports to skip unmaterializable objects while continuing to process exact source components.

Changes Reviewed:

  • ✅ Core logic change in buildObjectEntries correctly classifies metadata load failures as unsupported
  • ✅ Test expectations updated to match the new behavior
  • ✅ Documentation updated to clarify the handling of objects with unloadable ADT metadata
  • ✅ All 192 ADK tests and 26 adt-flow tests passing

The implementation aligns with the design principle that objects explicitly classified as unsupported should be skipped with diagnostics rather than blocking the entire transport. No blocking issues identified.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

@codacy-production

codacy-production Bot commented Aug 12, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 5 complexity · 4 duplication

Metric Results
Complexity 5
Duplication 4

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Comment thread packages/adk/src/transport-source-manifest.ts
@nx-cloud

nx-cloud Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit 31bd06a

Command Status Duration Result
nx affected -t lint test build e2e-ci --verbose... ✅ Succeeded 1m 57s View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗


☁️ Nx Cloud last updated this comment at 2026-08-12 08:20:20 UTC

@devin-ai-integration
devin-ai-integration Bot marked this pull request as draft August 12, 2026 08:17
…r path

Co-Authored-By: Petr Plenkov <petr.plenkov@gmail.com>
@ThePlenkov
ThePlenkov marked this pull request as ready for review August 12, 2026 08:19
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@ThePlenkov
ThePlenkov merged commit afdb26d into main Aug 12, 2026
27 checks passed
@ThePlenkov
ThePlenkov deleted the fix/skip-unmaterializable-objects branch August 12, 2026 08:21
@gitar-bot

gitar-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

Gitar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

baz: pending size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant