Use read action to access documents #850 #979
Merged
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.
Description
I could not reproduce issue #850, but it seems like the exception occurs because the read lock is not acquired. In this MR I add the read lock acquisition for accessing the Document instances.
Type of Change
How Has This Been Tested?
Manual Scenario
It is important that after this change util class generation still functions normally. I manually checked how it works in different possible cases.
org.utbot.examples.structures.StandardStructures
(without mocks) - util class with no mock support is generatedorg.utbot.examples.mock.CommonMocksExample
(mock strategy: mock class environment) - util class generated at previous step is updated to support mocksorg.utbot.examples.objects.AnonymousClassesExample
into a different test source root of the same module - util methods are imported from the existing util class from another test source root (no new util class is created)Checklist (remove irrelevant options):