Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
enterprise/server
clustered_conversation_manager.py					693
saas_nested_conversation_manager.py
openhands/runtime/impl/action_execution
action_execution_client.py					129, 132-141
openhands/runtime/impl/remote
remote_runtime.py					417-433
openhands/runtime/plugins/jupyter
__init__.py					46-50
openhands/runtime/plugins/vscode
__init__.py					48-53, 93-96
openhands/runtime/utils
bash.py					210
command.py
openhands/utils
http_session.py					27-31
Project Total

This report was generated by python-coverage-comment-action

@OpenHands please fix the failing actions on PR #11013 at branch allow-custom-user

I'm on it! chuckbutkus can track my progress at all-hands.dev

I started investigating the failing GitHub Actions on PR #11013 for the "allow-custom-user" branch. Here's what I found:

Analysis Summary

I examined the PR changes which add support for custom user configuration through environment variables:

• RUNTIME_USERNAME - allows specifying a custom runtime username
• RUNTIME_UID - allows specifying a custom runtime user ID
• SU_TO_USER - controls whether to use su commands (defaults to true)

The changes affect multiple files including runtime plugins (Jupyter, VSCode), bash session handling, command execution, and enterprise server components.

Testing Results

Linting Status: ✅ PASSED

• Ran the full pre-commit linting suite with pre-commit run --config ./dev_config/python/.pre-commit-config.yaml --all-files
• All linting checks passed successfully (trim whitespace, YAML validation, ruff, mypy, etc.)

Python Tests Status: ⏸️ INTERRUPTED

• Was about to run the Python tests to identify specific test failures when the session was stopped

Next Steps Needed

To complete the fix for the failing GitHub Actions, the following steps would need to be completed:

1. Run Python Tests: Execute the test suite to identify which specific tests are failing
2. Fix Test Issues: Address any test failures related to the custom user functionality
3. Verify Fixes: Re-run both linting and tests to ensure all issues are resolved
4. Commit & Push: Push the fixes to update the PR

Since the linting is already passing, the failures are likely in the Python test suite, possibly related to the new environment variable handling or user switching logic in the runtime components.

_{View full conversation}

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Lint

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #11013 at branch `allow-custom-user`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}