Fix v1.6.5 psutil runtime dependency issue #44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add py3-psutil as runtime dependency in .melange.yaml to fix ModuleNotFoundError during server initialization - Remove CI skip from test_production_container_mcp_protocol to ensure this type of regression is caught in CI before release - The test now runs in CI and would have caught the missing psutil dependency that caused v1.6.5 initialization failures
- Check if container image exists before trying to use it - Skip gracefully if image not available instead of hard failing - This allows the test to run in CI while providing clear guidance when container needs to be built first
chris-sanders
force-pushed
the
fix-v1.6.5-psutil-regression
branch
from
7dda8d3 to
13a14d9
Compare
This removes the confusion between manual venv creation with uv pip install and then using uv run commands, which could cause version conflicts.
The uv sync command uses ruff 0.11.8 (from lockfile) while uv pip install was using ruff 0.12.5, causing formatting differences between local and CI.
This ensures CI and local development use the same tool versions, avoiding formatting inconsistencies between ruff 0.11.8 and 0.12.5.
chris-sanders
added a commit
that referenced
this pull request
Aug 11, 2025
* Fix v1.6.5 psutil runtime dependency issue - Add py3-psutil as runtime dependency in .melange.yaml to fix ModuleNotFoundError during server initialization - Remove CI skip from test_production_container_mcp_protocol to ensure this type of regression is caught in CI before release - The test now runs in CI and would have caught the missing psutil dependency that caused v1.6.5 initialization failures
chris-sanders
added a commit
that referenced
this pull request
Aug 11, 2025
* Fix v1.6.5 psutil runtime dependency issue - Add py3-psutil as runtime dependency in .melange.yaml to fix ModuleNotFoundError during server initialization - Remove CI skip from test_production_container_mcp_protocol to ensure this type of regression is caught in CI before release - The test now runs in CI and would have caught the missing psutil dependency that caused v1.6.5 initialization failures
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Root Cause
The v1.6.5 release introduced psutil to replace ps/pkill subprocess calls, but psutil was only included in the build environment, not as a runtime dependency. This caused the compiled binary components of psutil to be missing from the final container image, leading to
ModuleNotFoundError: No module named 'psutil'during server initialization.Test Plan
test_production_container_mcp_protocolnow catches the error locallyValidation
The previously failing test now passes:
This fix ensures: