-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
Cannot cache build in the presence of __FILE_FULL_PATH__
#2840
Comments
Just for the record, rdmd uses a global cache too (in |
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 7, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 7, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 7, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 7, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 7, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 9, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Geod24
added a commit
to Geod24/dub
that referenced
this issue
Feb 9, 2024
By including the package path in the buildid we avoid the problem, at the expense of not sharing the cache for packages that could be shared, but we would need to know if the code depends on __FILE__ and __FILE_FULL_PATH__ or not.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reported by @kinke .
Results in:
Because the program does not get rebuilt.
The text was updated successfully, but these errors were encountered: