Skip to content

Fix PrimeIntellect query_instances TypeError on retry_if_missing#9259

Merged
kyuds merged 3 commits into
skypilot-org:masterfrom
kaiisfree:fix/primeintellect-query-instances-retry-if-missing
Apr 6, 2026
Merged

Fix PrimeIntellect query_instances TypeError on retry_if_missing#9259
kyuds merged 3 commits into
skypilot-org:masterfrom
kaiisfree:fix/primeintellect-query-instances-retry-if-missing

Conversation

@kaiisfree
Copy link
Copy Markdown
Contributor

Summary

  • Fixes PrimeIntellect error when deploying #9256
  • The PrimeIntellect provider's query_instances() was missing the retry_if_missing keyword argument that the base provisioner interface passes to all cloud providers
  • This caused a TypeError: query_instances() got an unexpected keyword argument 'retry_if_missing' when querying cluster status after launch

Fix

Added the retry_if_missing: bool = False parameter to query_instances() in sky/provision/primeintellect/instance.py, matching all other provider implementations.

Test plan

  • Verified all other providers (AWS, GCP, Kubernetes, Lambda, RunPod, vSphere, Cudo, Nebius, Yotta, Slurm) include this parameter
  • The parameter is unused in the PrimeIntellect implementation (same as most other providers), so the del pattern is used to suppress lint warnings

🤖 Generated with Claude Code

The PrimeIntellect provider's query_instances() was missing the
retry_if_missing parameter that the base interface expects, causing a
TypeError when SkyPilot tried to query cluster status.

Fixes skypilot-org#9256

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

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 updates the query_instances function signature in the Prime Intellect provisioner by adding the retry_if_missing parameter. However, the function signature remains incomplete as it is missing the cluster_name parameter required by the base provisioner interface, and the internal status_map lacks the PROVISIONING status, which could lead to runtime errors.

Comment thread sky/provision/primeintellect/instance.py
…s mapping

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kaiisfree
Copy link
Copy Markdown
Contributor Author

Good catches — both fixed in the latest commit:

  1. Added missing cluster_name: str parameter (aligned with all other provider implementations)
  2. Added PROVISIONINGClusterStatus.INIT to status_map (was listed in the file's status comment but missing from the mapping)

Both were pre-existing bugs that this PR now addresses alongside the original retry_if_missing TypeError fix.

@kyuds kyuds self-requested a review April 6, 2026 21:32
Comment thread sky/provision/primeintellect/instance.py Outdated
Copy link
Copy Markdown
Collaborator

@kyuds kyuds left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for the fix!

@kyuds kyuds enabled auto-merge (squash) April 6, 2026 21:35
@kyuds kyuds merged commit dddfe09 into skypilot-org:master Apr 6, 2026
21 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.

PrimeIntellect error when deploying

2 participants