Skip to content

Add verify provider lifecycle to CLI#2207

Merged
deep1401 merged 5 commits into
mainfrom
add/verify-provider-lifecycle
May 29, 2026
Merged

Add verify provider lifecycle to CLI#2207
deep1401 merged 5 commits into
mainfrom
add/verify-provider-lifecycle

Conversation

@deep1401
Copy link
Copy Markdown
Member

No description provided.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 25, 2026

Deploy Preview for transformerlab canceled.

Name Link
🔨 Latest commit fb43c00
🔍 Latest deploy log https://app.netlify.com/projects/transformerlab/deploys/6a19e705493ad50008c7b140

@polarityinc
Copy link
Copy Markdown

polarityinc Bot commented May 25, 2026

Paragon Summary

This pull request review analyzed 5 files and found no issues. The review examined code changes, potential bugs, security vulnerabilities, performance issues, and code quality concerns using automated analysis tools.

Paragon did not detect any problems in the current diff. Proceed with merge after your normal checks.

Adds a lab provider verify-lifecycle CLI command that verifies a compute provider's end-to-end lifecycle by launching a storage probe job and polling for its sentinel file in shared storage, including tests and a version bump to 0.0.56.

Key changes:

  • Added lab provider verify-lifecycle CLI command: launches a storage probe job and polls for a sentinel file in shared storage to confirm the provider can execute jobs end-to-end
  • New command supports --no-wait (fire-and-forget), --poll-interval, and --max-polls options for tuning probe behavior
  • Added 3 pytest tests covering success path, timeout failure, and --no-wait mode
  • Updated CLI version from 0.0.55 to 0.0.56 in pyproject.toml and uv.lock
  • Documented the new command in the CLI skills reference (SKILL.md)

Confidence score: 5/5

  • This PR has low risk with no critical or high-priority issues identified
  • Score reflects clean code review with only minor suggestions or no issues found
  • Code quality checks passed - safe to proceed with merge

5 files reviewed, 0 comments


Tip: @paragon-run <instructions> to chat with our agent or push fixes!

Dashboard

print(json.dumps({"job_id": job_id, "status": "launched"}))
else:
console.print(f"[success]✓[/success] Storage probe launched as job [bold]{job_id}[/bold].")
console.print(f" Check with: lab provider verify-lifecycle {provider_id} (or inspect job {job_id}).")
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.

Is this true? I thought this would launch a new job? Could just make this say check the job?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

You're right, re-running verify-lifecycle launches a fresh probe job rather than checking this one. Fixed the message to point at the job directly: Inspect it with: lab job info {job_id}.

Comment thread cli/src/transformerlab_cli/commands/provider.py
Comment thread cli/src/transformerlab_cli/commands/provider.py
Comment thread .agents/skills/transformerlab-cli/SKILL.md Outdated
@deep1401 deep1401 requested a review from dadmobile May 26, 2026 18:42
Copy link
Copy Markdown
Member

@dadmobile dadmobile left a comment

Choose a reason for hiding this comment

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

Changes look good. There are merge conflicts but I'm going to approve so you can merge after you fix them.

@deep1401 deep1401 merged commit beb26f4 into main May 29, 2026
14 checks passed
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.

2 participants