Concurrent blame with more unit tests and degraded annotation options when retrying. #15
Conversation
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
According to the documentation, P4Java is "basically thread-safe" and that "you can have multiple threads working against a single IServer object simultaneously".
…orce into concurrent-blame
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change is based on a branch made from this pull request. For reasons I cannot explain, a few of the files in our code base cannot be annotated when 'ignore white space' or 'follow integration' options are set (this is also true for the p4 command line tool, not just the p4java library). With this change, the plugin will disable these options before the next attempt to annotate a file. I also added a couple of unit tests for this change.