Skip to content

fix(marketplace-auto-review): validate-schema always exits 0#1643

Merged
coleam00 merged 1 commit into
devfrom
fix/validate-schema-always-exit-zero
May 11, 2026
Merged

fix(marketplace-auto-review): validate-schema always exits 0#1643
coleam00 merged 1 commit into
devfrom
fix/validate-schema-always-exit-zero

Conversation

@coleam00

@coleam00 coleam00 commented May 11, 2026

Copy link
Copy Markdown
Owner

Lets decide/act route schema-invalid submissions to request_changes with a comment instead of crashing the DAG. Fourth iteration of marketplace-auto-review end-to-end debugging.

Summary by CodeRabbit

  • Bug Fixes
    • Improved validation workflow behavior to always complete successfully and pass results to downstream processing nodes, enabling them to handle validation outcomes and post validation feedback as PR comments instead of stopping early. Previously, validation failures would cause the entire workflow to crash without providing users with detailed feedback.

Review Change Stack

…e can route invalid submissions

validate-schema was exiting 1 when any submitted workflow YAML failed schema validation. The DAG executor treats non-zero exit as node failure, which short-circuits the downstream ai-review / decide / act nodes via trigger_rule. Result: a marketplace PR with an invalid workflow gets no review comment because the workflow crashes before act can post one. Exit 0 always — the JSON output already includes 'valid: false', and decide routes that to 'request_changes' with an actionable comment.
@coleam00 coleam00 merged commit 17437bd into dev May 11, 2026
@coleam00 coleam00 deleted the fix/validate-schema-always-exit-zero branch May 11, 2026 16:36
@coderabbitai

coderabbitai Bot commented May 11, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7b9ab6ec-0a37-4a6a-9598-278707fd511e

📥 Commits

Reviewing files that changed from the base of the PR and between de87237 and 42eaf52.

📒 Files selected for processing (1)
  • .archon/scripts/marketplace-validate-schema.ts

📝 Walkthrough

Walkthrough

The validation script's exit behavior is modified to always return status code 0 after outputting JSON validation results, rather than exiting with code 1 on validation failures. This enables downstream DAG nodes to receive and process the validation flag independently.

Changes

Validation Exit Code

Layer / File(s) Summary
Exit Code Behavior
.archon/scripts/marketplace-validate-schema.ts
Conditional failure exit is replaced with unconditional process.exit(0) after result output, allowing downstream nodes to consume validation results.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

A rabbit hops through validation's gate,
No crash or fail—just status straight!
Exit code zero, bright and true,
Downstream nodes will have their clue. 🐰✨

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/validate-schema-always-exit-zero

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 and usage tips.

@Wirasm Wirasm mentioned this pull request May 12, 2026
cropse pushed a commit to cropse/Archon that referenced this pull request May 19, 2026
…e can route invalid submissions (coleam00#1643)

validate-schema was exiting 1 when any submitted workflow YAML failed schema validation. The DAG executor treats non-zero exit as node failure, which short-circuits the downstream ai-review / decide / act nodes via trigger_rule. Result: a marketplace PR with an invalid workflow gets no review comment because the workflow crashes before act can post one. Exit 0 always — the JSON output already includes 'valid: false', and decide routes that to 'request_changes' with an actionable comment.
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