You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Importing a new version of the data fails when a cached version exists due to importBugSigDB() failing to remove the previously cached version of the dataset. This error occurs on Windows (but appears to not occur on Linux or Mac).
Reproducible example
Run this twice on Windows and you will see the error message the second time:
Looks like there is something funny going on with the file path mixing forward slashes and backslashes. Maybe some use of paste instead of file.path. I'll take a look the next time I have access to a windows machine (likely tomorrow).
lgeistlinger
changed the title
[BUG] importBugSigDB() fails because unable to remove previously cached version
Warning in importBugSigDB() when updating a previously cached version (windows-only)
Feb 5, 2023
Sorry for the long wait. Finally got access to a windows machine. I couldn't reproduce the issue as described. I did see the reported warning message (note: a warning, not an error) when using importBugSigDB with cache = FALSE though.
The problem was that BiocFileCache::bfcdownload tried to delete a temporary file that was read with vroom::vroom, which triggered a warning that seems to appear only on windows (as previously described in tidyverse/vroom#177). Note that the functionality of importBugSigDB was never compromised, as calling importBugSigDB with cache = FALSE did overwrite your local copy in your cache, but failed to remove a temporary file at clean-up. This is now resolved in 1b86edd.
Importing a new version of the data fails when a cached version exists due to
importBugSigDB()
failing to remove the previously cached version of the dataset. This error occurs on Windows (but appears to not occur on Linux or Mac).Reproducible example
Run this twice on Windows and you will see the error message the second time:
R session information
The text was updated successfully, but these errors were encountered: