The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
bugfix for Zenodo resolver to search all versions
bugfix for local cache / content store handling of hashes other than SHA-256
software heritage is no longer a default registry. SWH imposes rate limiting of 120 calls, and so should not be pinged if not expected as a registry.
a new function, swh_ratelimit()
, can show the
remaining available calls and the remaining time until rate limit is
incremented (rate limit resets gradually.) Users may use this new
function when explicitly working against the SWH API to program their
own retry attempts appropriately.
purge_cache()
behavior improved.
resolve()
all donttest examples set temporary storage instead of trusting
that CRAN is setting R_USER_DATA_DIR for
tools::R_user_dir()
to an appropriate setting for running
donttest examples.
Include an additional hash-archive-like registry in
default_registries()
(https://hash-archive.carlboettiger.info)
default_registries()
is now an exported
function.
Some edits for robustness: tsv-backed
registries
disable vroom
altrep, (which can create file-lock issues on
Windows. Even though altrep reading can provide significant speed
improvements in this context with a large local registry, using LMDB for
that case will still be much faster.)
Minor adjustments to some function names:
query_sources()
is now renamed
sources()
query_history()
is renamed
history_url()
query
, query_sources()
, and
`query_history()
still present but flagged for
deprecationpin
still present but marked for deprecationpurge_cache()
to easily free space used by
contentidvroom
quietlystore()
and
retrieve()
content_id()
now returns a chr vector instead of a
data.frame unless multiple algos are requested.NEWS.md
file to track changes to the
package.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.