Skip to content

fix(dag): report corrupted DAGs in compact/json output formats#228

Open
davidweb3-ctrl wants to merge 4 commits intoCortexLM:mainfrom
davidweb3-ctrl:fix-dag-error-handling
Open

fix(dag): report corrupted DAGs in compact/json output formats#228
davidweb3-ctrl wants to merge 4 commits intoCortexLM:mainfrom
davidweb3-ctrl:fix-dag-error-handling

Conversation

@davidweb3-ctrl
Copy link
Copy Markdown

Summary

Fixes inconsistent error handling where corrupted DAGs were silently hidden in --format compact and --format json, while --format text correctly showed error indicators.

Bug Description

When a DAG state file is corrupted (invalid JSON):

Format Before (Wrong) After (Fixed)
text ? bad (error loading) ? bad (error loading)
compact (nothing, exit 0) ? bad (error loading)
json [], exit 0 [{"id": "bad", "error": "error loading"}]

Root Cause

The compact and json format handlers only handled the Ok(dag) case and silently skipped errors:

Changes

  • JSON format: includes error objects for corrupted DAGs
  • Compact format: prints error indicators matching text format
  • Text format: unchanged (already correct)

Fixes: PlatformNetwork/bounty-challenge#47965

When bumping from a prerelease version (e.g., 1.0.0-beta.1),
the script now correctly transitions to the stable version
instead of incrementing and skipping the stable release.

Changes:
- Detect if current version is a prerelease (contains '-')
- For prerelease versions: patch/minor/major bumps now return
the base stable version (e.g., 1.0.0-beta.1 -> 1.0.0)
- For stable versions: behavior unchanged (normal increment)

Fixes: PlatformNetwork/bounty-challenge#47839
The script was looking for cortex-cli/Cargo.toml at the repository root,
but the crate is actually located at src/cortex-cli/Cargo.toml per the
workspace configuration.

This caused the version validation check to be silently skipped,
as the file existence check failed.

Changes:
- Updated CORTEX_CLI_CARGO path from cortex-cli/Cargo.toml to src/cortex-cli/Cargo.toml

Fixes: PlatformNetwork/bounty-challenge#47866
Copy link
Copy Markdown

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

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

Labels

None yet

Projects

None yet

1 participant