-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Bug]: Runtime Directory Hash Mismatch #3767
Comments
The "fix" here could be as simple as using the same-named temp directory (to place the sdist in) before creating hashes as apparently any different path also changes the hash. |
@tobitege i think the issue was a little bit trickier than i initially thought - we copy a different subset of folders into |
eww that complicates things even more 😔 |
Is there an existing issue for the same bug?
Describe the bug
The directory hash calculated for Runtime API does not match when calculate in different environments.
For example, In this CI: https://github.com/All-Hands-AI/OpenHands/actions/runs/10739603421/job/29785986651
When building the images (Build Image (nikolaik/python-nodejs:python3.11-nodejs22, nikolaik)), we have
4859922960d366c29664226abe370db3
as hash:But in the same exact code base but in different environments Test Runtime (nikolaik), we got
b0f3fa5e3c2a114044e2e3a74827aa99
as new hash:The mismatch of this hash will cause issues: if the user is launching OpenHands with
docker run,
it will likely generate a different dir hash, making the user have to re-build the runtime image the first time they launch viadocker run.
Current OpenHands version
Installation and Configuration
Model and Agent
No response
Operating System
No response
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
No response
The text was updated successfully, but these errors were encountered: