Closed rikhuijzer closed 8 months ago
Maybe we should just cache .julia/datadeps
by default too because my counterargument in https://github.com/julia-actions/cache/issues/40#issuecomment-1369791345 doesn't hold anymore now with the new system.
Yeah I guess we could add a custom field. See #74
The same argument came up for the makie dir in the depot but people pointed out Makie should use scratchspaces.
Is there a reason why DataDeps doesn't use scratchspaces?
Is there a reason why DataDeps doesn't use scratchspaces?
It seems not https://github.com/oxinabox/DataDeps.jl/issues/135
Ok. Let's do that then. Then we don't have to get people do a manual step.
Ok. Let's do that then. Then we don't have to get people do a manual step.
Yes you're right. That would be the best solution 👍 Do you have time to open a PR to DataDeps? Otherwise, I'll probably pick it up somewhere next week
Until that's fixed in DataDeps you can either downgrade to cache@v1.3
or keep v1
and force cache-compiled: false
(but both require remembering to revert the change once it's fixed)
Until that's fixed in DataDeps you can either downgrade to
cache@v1.3
or keepv1
and forcecache-compiled: false
(but both require remembering to revert the change once it's fixed)
Sounds good 👍 Thanks. I'll close this as the issue is at the DataDeps side.
I got the following error after switching to the new cache system:
when calling
datadep"SomeDep"
.@IanButterworth do you know why this might start to fail now? Is
~/.julia
now readonly while it wasn't?I am quite sure that this is caused by the switch to the new system. I had this crash before and then I switched back to
julia-actions/cache@v1.3.0
and removed all caches. Today, I tried the newjulia-actions/cache
again and got the same error.Issue https://github.com/julia-actions/cache/issues/40 is slightly related. It also talks about DataDeps.