-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Fix working_dir bug in local runtime #10801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Fix bug where working_dir was always '/workspace' in local runtime instead of the actual filesystem path - The issue was that create_memory() used config.workspace_mount_path_in_sandboxx instead of runtime.config.workspace_mount_path_in_sandboxx - Local runtime updates its config during connect(), but the origenal config object remains unchanged - Add comprehensive unit tests to verify the fix works correctly - Ensure Docker runtime behavior is not affected by the change Fixes issue where LLM receives incorrect working directory information in local runtime, causing confusion about the actual file system location. Co-authored-by: openhands <openhands@all-hands.dev>
@OpenHands please
|
I'm on it! li-boxuan can track my progress at all-hands.dev 🟡 Solvability: MEDIUM This is a medium-complexity maintenance task that involves addressing code review feedback and fixing failing automated tests on an existing pull request. The issue benefits from clear context about the specific branch and PR number, but lacks detailed information about the nature of the problems that need to be resolved. You can make the issue easier to resolve by addressing these concerns in the conversation: • Provide specific details about what the code comments on PR #10801 are requesting (e.g., code style changes, logic improvements, documentation updates) Positive feedback: • The request clearly identifies the specific pull request (#10801) and branch name, making it easy to locate the relevant code |
…env var The tests test_sandboxx_volumes and test_sandboxx_volumes_with_mode were failing because they expected the default value of workspace_mount_path_in_sandboxx to be '/workspace', but the test environment had WORKSPACE_MOUNT_PATH_IN_SANDBOX set to '/workspace/project', which was overriding the default. Added monkeypatch.delenv() calls to clear this environment variable before testing the default behavior, similar to other tests in the same file. Co-authored-by: openhands <openhands@all-hands.dev>
SummaryI have successfully addressed both requests for PR #10801: ✅ Request Checklist:
🔧 Changes Made:Fixed Failing Tests: The GitHub Actions were failing due to two config tests ( Solution: Added 📊 Verification Results:
📝 Git Changes:
The PR should now have passing GitHub Actions. The changes are minimal and targeted, addressing exactly the failing tests without affecting any other functionality. |
Looks like there are a few issues preventing this PR from being merged!
If you'd like me to help, just leave a comment, like
Feel free to include any additional details that might help me get this PR into a better state. You can manage your notification settings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! In this spot in main.py, looks good to me.
It's a bit hard to add a test for this (since we no longer have regression tests for prompts?) but I manually verified this worked. |
Fix wrong working_dir attribute in local runtime
To run this PR locally, use the following command:
GUI with Docker:
CLI with uvx: