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

Fix --continue, improve and rename persistentID #937

Merged
merged 30 commits into from
Jan 28, 2022

Conversation

lfcnassif
Copy link
Member

@lfcnassif lfcnassif commented Jan 25, 2022

Closes #784, closes #792 and closes #941:

  • make sure item ids are not used before possibly being reassigned when resuming processing adding a number of checks;
  • improves persistentID computation using carvedId, add checks for required params used in the formula;
  • fixes a possible parent-child relationship issue when resuming processing of recursive embedded virtual disks (master);
  • replace parentIdInDataSource requirement (and methods) for parentGlobalID presence in all items;

Still need to do more tests...

@lfcnassif lfcnassif force-pushed the #784_improve_and_rename_globalID branch 2 times, most recently from 2be79a5 to 0aa4519 Compare January 25, 2022 23:33
@lfcnassif lfcnassif changed the title #784 improve and rename persistentID Fix --continue, improve and rename persistentID Jan 26, 2022
- this property is needed when resuming processing to get a previous
parent id referenced by subitems which parents were not commited, then
when reprocessing parents, their id can be updated to the previous
value, so parent-child relationships will be preserved.
- fix embedded disks subitems references to parentGlobalID
- could make subitems of embedded disks decoded again to be added twice
@lfcnassif lfcnassif force-pushed the #784_improve_and_rename_globalID branch from f91e560 to 3859c57 Compare January 26, 2022 20:29
@lfcnassif
Copy link
Member Author

I changed commit messages to point to correct newly created issues and just force-pushed, sorry if someone checked out this branch.

@lfcnassif lfcnassif force-pushed the #784_improve_and_rename_globalID branch from 2c8180c to 0c724c8 Compare January 28, 2022 21:57
@lfcnassif
Copy link
Member Author

lfcnassif commented Jan 28, 2022

This was harder than expected, but I think now --continue is working fine. I'll run a final large processing test before merging.

@lfcnassif lfcnassif marked this pull request as ready for review January 28, 2022 22:02
@lfcnassif lfcnassif merged commit 0c724c8 into master Jan 28, 2022
@lfcnassif lfcnassif deleted the #784_improve_and_rename_globalID branch January 28, 2022 23:54
@lfcnassif
Copy link
Member Author

lfcnassif commented Jan 29, 2022

@hauck-jvsh and @tc-wleite, this took from me much more time than I would like. I'll be on vacation next week. When I return, I will focus on your ready PRs, thanks!

PS: At least it was beautiful to me finally seeing --continue working fine when processing an evidence with multiple recursively embedded disks, interrupted a lot of times :-)

@hauck-jvsh
Copy link
Member

hauck-jvsh commented Jan 29, 2022

Sure, relax and enjoy your vacation. Just to be sure, after this there will be the globalId and the trackId?

@wladimirleite
Copy link
Member

Enjoy your vacation, @lfcnassif!

@lfcnassif
Copy link
Member Author

Sure, relax and enjoy your vacation. Just to be sure, after this there will be the globalId and the trackId?

Yes. Thank you two!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants