Skip to content

Fix environment discovery failure on unsupported platforms (fixes #39) - #52

Open
SheepTAO wants to merge 1 commit into
prefix-dev:mainfrom
SheepTAO:fix-unsupported-envs
Open

SheepTAO wants to merge 1 commit into
prefix-dev:mainfrom
SheepTAO:fix-unsupported-envs

Conversation

@SheepTAO

Copy link
Copy Markdown

Description

Fixes #39.

When a project contains environments targeting platforms not supported by the current host (e.g. dev-gpu with CUDA on a CPU-only node), pixi list -e <env> exits with an error.

Previously, this unhandled error inside Promise.all caused the entire environment refresh to fail and return [], hiding all valid environments.

Changes

  • Wrap listPixiPackages in a try-catch inside refreshPixi, logging the Pixi error directly and skipping unsupported environments cleanly.
  • Add error handling to PixiPackageManager.refresh to prevent unhandled rejections during background package refresh.
  • Support relative paths and ${workspaceFolder} in pixi-code.pixiExecutable.
  • Provide default workspace cwd fallback in runPixi.

…relative pixi path

- Catch errors during environment package listing and log pixi output directly to prevent total discovery failure
- Support relative paths and ${workspaceFolder} in pixi-code.pixiExecutable setting
- Provide default cwd fallback in runPixi
- Add error boundary to PixiPackageManager.refresh
- Update README.md, CHANGELOG.md, and bump version to 0.2.1
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.

Failure when manifest contains non-native architecture environment

1 participant