Fixed bug with the Catalogue AsynchronousSaver #2621
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.
I experienced this issue during my documentation revamp, where the screengrab app is now loading multiple scripts which use Catalogues, all within a single session. A Catalogue which had been removed from the script was still trying to save images, despite the file it wanted to write being dependent on the script variables. We now prevent saving in this obscure case.
Note that while I didn't change
CatalogueTest.testDeleteBeforeSaveCompletes
here, as best I can tell it isn't doing what it claims. The async save happens so quickly that the save completes before the catalogue is deleted (confirmed via prints inside the saver), so I've taken an alternate approach in my new test case.