-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* initial implementation of project.close() for now: close coreManager cores for every namespace * add `close` to Datastore, use `coreManager.close()` the close method of `Datastore` basically `.removeAllListeners()` and `close()` over the `#coreIndexer` instance. I don't if that should be enough? But looking at the class, it seems so... * add sqlite as a private field, `.close()` it on `MapeoProject.close()` * close dataStores in parallel * await #coreManager.close and dataStore promises * update multi-core-indexer to alpha8 * update lock * fix package-lock, add tests to close * fix `.getMany` test for `project.close()` * add tests for creating project after `project.close()` * * remove 'multiCoreIndexer.removeAllListener()' (the class is already removing added listeners) * comment crud test regarding closing and re-opening a project * remove cached project in manager after closing project * remove added listeners in mapeo project after close * [OPTIC-RELEASE-AUTOMATION] release/v9.0.0-alpha.3 (#404) Release v9.0.0-alpha.3 Co-authored-by: achou11 <[email protected]> * Revert "[OPTIC-RELEASE-AUTOMATION] release/v9.0.0-alpha.3 (#404)" This reverts commit a1b742e. * update flaky sync e2e test now that project.close() is implemented * const instead of let in close() method * fix: close cores after indexing is closed --------- Co-authored-by: Tomás Ciccola <[email protected]> Co-authored-by: Andrew Chou <[email protected]> Co-authored-by: optic-release-automation[bot] <94357573+optic-release-automation[bot]@users.noreply.github.com> Co-authored-by: achou11 <[email protected]> Co-authored-by: Gregor MacLennan <[email protected]>
- Loading branch information
1 parent
e3695da
commit 06a4335
Showing
5 changed files
with
136 additions
and
14 deletions.
There are no files selected for viewing
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
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
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
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
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