Closed grimbough closed 8 months ago
Hm. The warnings should have been "fine" as gypsum falls back to file.copy()
when file.rename()
doesn't work. If file.copy()
didn't work either, there should have been an actual error before hitting HDF5.
gypsum 0.99.15 should fix it so that file.rename()
succeeds and doesn't emit warnings; but I still don't know why the HDF5 call ultimately fails, unless your file.copy()
is just quietly failing.
Do the files like /home/msmith/.cache/R/gypsum/bucket/scRNAseq/paul-hsc-2015/2023-12-20/row_data/basic_columns.h5
actually exist?
So I restarted everything and cleared all the caches, and now can't reproduce the error.
My first thought was that perhaps I had some funky version of rhdf5 loaded inadvertantly, since I'd been working on that, but that wouldn't explain why it worked when I switched cache location to the same drive :shrug:
Frustrating that I can't give any more details, but hopefully it was just a one off transient set of circumstances. I'll close for now and re-open if I encounter it again.
When trying to test my changes to rhdf5 for #44 I found I can't run the example code to load
PaulHSCData
on my machine.I presume the warings are important here as they all relate to an
'Invalid cross-device link'
. I've edited the output below for brevity, but the missing warnings are all similar just referencing different files.On my system the default cache location and
tmp
are on on different partitions, which feels like it might be related.If I explicitly choose the gypsum cache directory to be on the same drive as
/tmp/
then it seems to work fine:Here's the session info if that's helpful: