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
There is conflicting documentation about where the Attic should be. In the tutorial, it says that the attic should be here:
The Attic
Partial output or invalidated output from previous runs gets moved to $DEST/ducttape.attic/$TASK_NAME/$REALIZATON _ NAME/$WORKFLOW _ VERSION. This may help prevent accidental deletion of data and can help diagnose issues if tasks fail repeatedly. The workflow version is incremented every time the workflow is executed.
However, when I look at the scala code, it says that the attic is a hidden folder ".attic" under the config file's directory.
I still cannot find the attic. I've been using a directory structure that places both the .tape file and the .conf file in the same directory. Whenever I execute ducttape, a .versions directory is created, but this only contains a manifest, pid, and a copy of the .tape file.
The text was updated successfully, but these errors were encountered:
There is conflicting documentation about where the Attic should be. In the tutorial, it says that the attic should be here:
The Attic
Partial output or invalidated output from previous runs gets moved to $DEST/ducttape.attic/$TASK_NAME/$REALIZATON _ NAME/$WORKFLOW _ VERSION. This may help prevent accidental deletion of data and can help diagnose issues if tasks fail repeatedly. The workflow version is incremented every time the workflow is executed.
However, when I look at the scala code, it says that the attic is a hidden folder ".attic" under the config file's directory.
I still cannot find the attic. I've been using a directory structure that places both the .tape file and the .conf file in the same directory. Whenever I execute ducttape, a .versions directory is created, but this only contains a manifest, pid, and a copy of the .tape file.
The text was updated successfully, but these errors were encountered: