This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BV-1063436 and BZ-1045117: new project creates just one commit + fixi…
…ng double commits on file creation.
- Loading branch information
Showing
4 changed files
with
18 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a8ba1bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello,
shouldn't be the code between ioService.startBatch() and ioService.endBatch() in try-catch block? It seems that if an exception is thrown after the startBatch() and before endBatch(), the ioService will stay blocked forever and thus it won't be possible to create new commits. The finally block should then call endBatch() or in case of error just unlock the ioService.
Note: I haven't studied in deep the implementation of ioService.startBatch(), so I might be missing something.
a8ba1bb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@psiroky yes, you're completely right! i did this quickly to test, faced a different issue, and never return to fix original quick and dirty. thx!