Skip to content
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

Check if completed file should actually be copied back into the folder #23

Open
BrenekH opened this issue Jan 22, 2021 · 0 comments
Open
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@BrenekH
Copy link
Owner

BrenekH commented Jan 22, 2021

If a Job that is running is replaced with a new file(for example, the file is upgraded), Encodarr will still copy the completed file even though it is not relevant.

The problem is detecting this kind of change. A hash could be computed when the Job is dispatched/generated and checked again when the file is ready to be copied back. This only works for files named the same, but some file existence checks could supplement that as well.

Whatever the solution, it probably should be an option for the user.

@BrenekH BrenekH added the bug Something isn't working label Jan 22, 2021
@BrenekH BrenekH added good first issue Good for newcomers and removed Hacktoberfest labels Nov 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant