The idea of memory-backed caches that are shared between clients was a little half-baked. In general, that is not expected, and can cause issues with tests (see https://github.com/openforcefield/openff-qcsubmit/issues/275). This makes that kind of shared cache opt-in.
Not that there is still some idea of sharing the cache withing a particular client due to multi-threading. But now, unless specified, constructing a new client will result in a separate cache.
Also fixes an issue where, if some records were in cache and some not, an exception was raised due to client mismatches between records.
Changelog description
Fixes issues related to shared caching. Shared in-memory caches are now opt-in
Description
The idea of memory-backed caches that are shared between clients was a little half-baked. In general, that is not expected, and can cause issues with tests (see https://github.com/openforcefield/openff-qcsubmit/issues/275). This makes that kind of shared cache opt-in.
Not that there is still some idea of sharing the cache withing a particular client due to multi-threading. But now, unless specified, constructing a new client will result in a separate cache.
Also fixes an issue where, if some records were in cache and some not, an exception was raised due to client mismatches between records.
Changelog description
Fixes issues related to shared caching. Shared in-memory caches are now opt-in
Status