Enforce the removal of filenames to be checked #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear Jonela
Thanks a lot for your Jacksum and HashGarten system, I like it a lot.
Issue to report: I encountered a persistent parameter/property problem when using HashGarten/Jacksum Version 2.9.0 on Windows 11 (Version 24H2, OS Build 26100.4652).
My Task: I had to check a couple of deliveries mainly with content and md5-verification files that contained relative paths. Please check the following steps-to-reproduce
Prerequisite
sample-files.zip
Part one
Directly open HashGarten (not with "Send to")
Go to Output Style > Pathstyle: set to "relativize paths to" and give the absolute path of the content folder to be checked.
Go to menu Operation Mode > Verify Hash Values
Add the content folder to be checked
Go to Calculation > Set the algorithm md5
Go to Output Style > Check Print header
Go to Output Files, set the output and error file
Press the "Verify Hash Values" Button
Await the message box "HashGarten task has been finished"
Check output: All good
(12. Keep HashGarten opened)
output-01.txt
error-01.txt
Empty.
Part two
Keep HashGarten opened
Rename the sample folder form Part one: jacksum-test01 -> jacksum-test01.removed. Just to make sure that it does not interfere with the next run.
Repeat steps Part One 2 - 09, but with the new sample folder jacksum-test02-nextrun, make sure to fix the relative path, content folder and verification file.
Check output: Failure
output-01.txt
error-01.txt
Note:
Even if all new values have been set for the 'nextrun', the error output shows that it still
refers to a file from the first run. In other words, something is persistent from to another run.
I'm not sure whether this happens only when dealing with verification files that use relative paths.
Suggested Fix
I tried to suggest a fix that is only in the HashGarten project. When testing the changes from this pull request, the procedure above succeeded. Of course I don't know whether this changes have undesired side effects. Probably there is a better location to fix the issue. If the fix is not OK, at least it gives you an idea of what I'm getting at.
Note: I could not test any "Send to" cases coming from a file manager.
Thanks for your attention.
Best Regards
baddonkey