Skip to content

Use explicit --manifest-path for pixi jobs instead of unsetting PIXI_PROJECT_MANIFEST#406

Open
mkitti wants to merge 1 commit into
mainfrom
mkitti-pixi-manifest-path
Open

Use explicit --manifest-path for pixi jobs instead of unsetting PIXI_PROJECT_MANIFEST#406
mkitti wants to merge 1 commit into
mainfrom
mkitti-pixi-manifest-path

Conversation

@mkitti

@mkitti mkitti commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • pixi's --manifest-path flag always overrides the PIXI_PROJECT_MANIFEST env var (verified against pixi 0.70.2), so this switches the generated pixi command to pixi run --manifest-path "$FG_MANIFEST_DIR" <task> instead of unsetting PIXI_PROJECT_MANIFEST and relying on cwd-based manifest discovery.
  • Introduces FG_MANIFEST_DIR, exported alongside FG_WORK_DIR in every generated job script (all app types, not just pixi), pointing at the directory containing the app's manifest.
  • Updates tests/test_apps.py to assert on the new preamble.

Supersedes #405 (moved from a fork branch to a branch within this repo).

Test plan

  • pixi run -e test test-backend — all 723 tests pass

🤖 Generated with Claude Code

…PROJECT_MANIFEST

pixi's --manifest-path flag always overrides the PIXI_PROJECT_MANIFEST
env var, so pointing pixi run at the manifest directory explicitly is
more robust than unsetting the env var and relying on cwd-based
discovery. Introduces FG_MANIFEST_DIR, exported alongside FG_WORK_DIR
for all job types.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@krokicki

krokicki commented Jul 8, 2026

Copy link
Copy Markdown
Member

Nice, I like it!

@krokicki

krokicki commented Jul 8, 2026

Copy link
Copy Markdown
Member

But I think we still need the unset PIXI_PROJECT_MANIFEST in there for now, because we don't want Fileglancer's manifest leaking into the cluster jobs.

I'm going to fix the ENV leakage on a separate PR.

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