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
Currently we're using a workaround to use the watchPath function in dsl2. this workaround still has limitations, as it requires us to touch -ca the file just to read it. this also has limitations, for example if we do not own or have permission to touch -ca.
This new factory should be able to replace the workaround. We should basically be able to set an interval and with each emission read an input file. This feature only seems to be available in the edge version right now.
for further context about why we needed a workaround in the first place, watchPath doesn't work by itself because it uses inotify, which requires the target of watchPath to be modified on the same machine as where nextflow is running. so if something is modified in one node of a cluster, and watchPath is running in another node, nothing will happen.
The text was updated successfully, but these errors were encountered:
See documentation here:
https://www.nextflow.io/docs/edge/channel.html#interval
Currently we're using a workaround to use the watchPath function in dsl2. this workaround still has limitations, as it requires us to
touch -ca
the file just to read it. this also has limitations, for example if we do not own or have permission totouch -ca
.This new factory should be able to replace the workaround. We should basically be able to set an interval and with each emission read an input file. This feature only seems to be available in the edge version right now.
for further context about why we needed a workaround in the first place, watchPath doesn't work by itself because it uses inotify, which requires the target of watchPath to be modified on the same machine as where nextflow is running. so if something is modified in one node of a cluster, and watchPath is running in another node, nothing will happen.
The text was updated successfully, but these errors were encountered: