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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
PVF validation host owns a cache of compiled artifacts. This cache is populated by preparation workers, sub-processes that perform some checks and compile the artifact.
Specifically, a preparation worker first creates a file in the temporary directory. Once compiled and wrote, the artifact is moved into its final location. We do this so that because other parts of
The move is performed with async_std::fs::rename which, similarly to std::fs::rename, relies on rename(2).
This will not work if the new name is on a different mount point.
Almost always /tmp has a different mount point than the node's basedir. My tests and test run on Rococo showed it worked well. I assume this is related to some special handling of tmpfs. Regardless, there was a report of this not working on Docker. It manifested in empty files copied into the artifact caches.
The text was updated successfully, but these errors were encountered:
PVF validation host owns a cache of compiled artifacts. This cache is populated by preparation workers, sub-processes that perform some checks and compile the artifact.
Specifically, a preparation worker first creates a file in the temporary directory. Once compiled and wrote, the artifact is moved into its final location. We do this so that because other parts of
The move is performed with
async_std::fs::rename
which, similarly tostd::fs::rename
, relies onrename
(2).From
std::fs::rename
:Almost always
/tmp
has a different mount point than the node's basedir. My tests and test run on Rococo showed it worked well. I assume this is related to some special handling of tmpfs. Regardless, there was a report of this not working on Docker. It manifested in empty files copied into the artifact caches.The text was updated successfully, but these errors were encountered: