You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Space stage mapping to use only ZenML standard deployment states
Addresses feedback about using non-standard deployment states. The previous
implementation introduced HuggingFace-specific stages (RUNNING_BUILDING,
NO_APP_FILE) into ZenML status mapping without properly handling all cases.
Changes:
- Import and use SpaceStage enum instead of string matching
- Map all 10 HuggingFace Space stages to ZenML's 5 standard states:
* RUNNING → RUNNING (only when fully provisioned)
* BUILDING, RUNNING_BUILDING → PENDING (health endpoint not available)
* BUILD_ERROR, RUNTIME_ERROR, CONFIG_ERROR, NO_APP_FILE → ERROR
* STOPPED, PAUSED, DELETING → ABSENT (exists but not running)
* Unknown stages → UNKNOWN (future-proofing)
Key fix: RUNNING_BUILDING now correctly maps to PENDING, not RUNNING, because
the health endpoint is not available during this rebuild phase.
Follows same pattern as GCP/AWS deployers which map external service states
to ZenML's standard deployment lifecycle states.
0 commit comments