-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix: Pip Installation Issue in Terminal #1707
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1707 +/- ##
=======================================
Coverage ? 63.83%
=======================================
Files ? 96
Lines ? 3877
Branches ? 0
=======================================
Hits ? 2475
Misses ? 1402
Partials ? 0 ☔ View full report in Codecov by Sentry. |
@xingyaoww could you take a look at this one? It seems reasonable but I'm not 100% sure about whether this is the right approach. |
Btw, I wonder if you have any screenshots / ways we could potentially reproduce this? |
I want to replicate the result of your example conversation, but I encountered an issue and noticed that others in the community have experienced the same problem. Here is my local log: I use GPT-4.
|
sorry, I accidentally clicked the wrong button. I have now reopened it. |
@jiangleo Oh yes!! I've definitely encountered this one.. But this seems a bit random to me - sometimes it works (like my screenshot), and sometimes it doesn't. If you could create a test case to reproduce this similar to this https://github.com/OpenDevin/OpenDevin/blob/main/tests/integration/test_agent.py#L73-L95, that would be awesome! We will then know if the issue is fixed by observing the test result. |
OpenDevin is an amazing project, and I'm happy to contribute! I will try to write an integration test for it. |
Fix sanbox
The latest PR has added integration test cases. This PR includes changes in three areas:
Additionally, even though the issue is fixed, restarting the kernel is still necessary. And, I have a few questions that need confirmation:
|
I have reproduced the error in the workflow locally, and I am preparing to try and resolve it. |
No - I don't think so -- it will just run on your own fork :)
I don't yet have a clue, maybe due to some sandbox issues? How do you run local integration tests? by running the |
… running the integration tests to ensure that the tests have no side effects.
… the LLM completion to fail.
fix: it is necessary to remove the installed packages and files after…
Yes. And to make it easier to write/run the new integration test, I set the environment variables
The issues with failed integration tests, both locally and in GitHub Actions, are due to two main causes: the statefulness of the sandbox environment and the prompt containing an excessively long installation log. To resolve these issues, I propose two solutions:
I have already resolved these issues in my forked OpenDevin. |
…h to upstream main state
Revert tests/integration/README.md and tests/integration/regenerate.s…
Merge remote-tracking branch 'upstream/main' into fix_sanbox
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.
LGTM!
This PR addresses a issue where the CodeAct Agent could not install any pip library through the terminal, though installations were possible via Jupyter.
Changes Made:
Dockerfile Update:
README Update:
This should resolve the installation issues and improve the overall setup consistency for all users. For reference, see the related issue discussed in the community: Issue #1627.