generated from snivilised/arcadia
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve the sampling workflow #116
Labels
feature
New feature or request
Comments
Did not trigger a build on the branch feat/improve-the-sampling-workflow |
plastikfan
added a commit
that referenced
this issue
Feb 26, 2024
plastikfan
added a commit
that referenced
this issue
Feb 26, 2024
migrated to go 1.22, which is now causing many lint errors to fire, that didnt so previouly, so these lint errors are bing fixed in this issue. |
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
plastikfan
added a commit
that referenced
this issue
Apr 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sample mode should not be considered transparent because typically the workflow would be:
If transparent, then the originals are noved to the trash location, but this is a problem for a sample run, since the user would have to manually retrieve the original back to source location and re-run. Transparency is only good for a full run.
We need a better workflow.
BEFORE A NON TRANSPARENT RUN, ANY SAMPLE FILES FOUND IN THE SAME DIR AS THE ORIGIN SHOULD BE MOVED TO THE --output LOCATION. THE REASON FOR THIS IS THE USER MAY PERFORM A TRANSPARENT SAMPLE RUN, FOLLOWED BY A NON TRANSPARENT FULL RUN. IN THIS CASE, THE SAMPLE FILES WILL BE IN THE WRONG LOCATION AND SHOULD BE MOVED TO THE --output
The text was updated successfully, but these errors were encountered: