Fix memo file regeneration #139
Merged
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
For the memo file regeneration utility, this is a requirement to be able to use the PixelsService.setMemoizerDirectoryLocal API
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.
#137 introduces a regression in the memo file regeneration workflow when passing a cache directory different than the default. 9fee5d0 fixes the issue by setting the value of the
isReadOnlyargument totruein the bean definition file. This flag is a requirement to use thePixelsService.setMemoizerDirectoryLocalAPI and was previously set internally in https://github.com/glencoesoftware/omero-ms-core/blob/d174a81f563d63f1b1690790554c60ca5b91a05a/src/main/java/com/glencoesoftware/omero/ms/core/PixelsService.java#L40.