-
Notifications
You must be signed in to change notification settings - Fork 326
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
Cached package is used instead of local version #1698
Comments
@mmdanggg2 Question about your expected behavior statement there, wouldn't the cached package take precedence over the local package depending on their order in your For example, I tested out on Windows two different config files:
and then:
When using the first config file, the selected package is at When using the first config file, the selected package is at I tested with Rez 2.113.0. |
I do indeed have |
So this would seem to be a much more difficult to catch bug than I originally thought, this package I have the problem with appears to have had the local version cached at some point. There are actually 2 different packages cached under the same version in the cache folder. So I guess then the bug is more that somehow somewhere rez decided to cache a local package. Just checked and this has seemingly happened to at least 3 packages so it's not completely one off either. |
So the plot thickens, these wrongly cached packages were not even cached by my user. A bit of background, we run a render farm where rez env is being run under different users on our workstations. Additionally, for reasons, the packages folder of my user is readable by other users. So my current theory as to what happened it that the render job started up as userB which spun up a rez-pkg-cache daemon as userB. At this same time I must have started a rez-env which will have resolved my local packages and added them to the list of packages to cache. These would usually then rejected by the cache daemon but, since the daemon was not running as my user but userB, those packages did not appear local to that user and so were cached. |
When a version of a package has been released and then cached, if I start to develop that package again in local with the same version number, the cached version of the payload is used instead of the one in local despite having
package_cache_local = False
Environment
To Reproduce
1. Setup rez package caching2. Release a package, foo-1.0
3.
rez-env foo
to cache the package4. Modify the package and
rez-build -i
to local5.
rez-env foo
again and see that while the local copy overrode the package definition, REZ_FOO_ROOT is pointing to the cacheExpected behavior
I expect that the local version would always take precedence over a cached version.
Actual behavior
The cached version takes precedence.
The text was updated successfully, but these errors were encountered: