Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use in-memory db #43

Merged
merged 1 commit into from
Apr 27, 2023
Merged

use in-memory db #43

merged 1 commit into from
Apr 27, 2023

Conversation

conorsch
Copy link
Contributor

Tries to use the new storage init logic to store sync state in memory, which should cause galileo to sync at service start.

@conorsch conorsch force-pushed the try-in-memory-db branch 2 times, most recently from d9c7787 to 6dbe1d8 Compare April 27, 2023 17:15
@conorsch conorsch requested a review from plaidfinch April 27, 2023 17:15
@conorsch conorsch changed the title partial: use in-memory db use in-memory db Apr 27, 2023
@conorsch
Copy link
Contributor Author

Updated based on discussion with @plaidfinch. Take a look?

Uses the new storage init logic [0] to store sync state in memory.
This will cause galileo to sync at service start to memory, and abjure
any on-disk storage.

Hat tip to @plaidfinch for explaining the type inference required by the
view service changes.

[0] penumbra-zone/penumbra#2372
@conorsch conorsch marked this pull request as ready for review April 27, 2023 18:15
Copy link
Contributor

@plaidfinch plaidfinch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should work! What's nice about this is that while it shares the custody file for whatever pcli wallet is currently present, it doesn't touch that wallet's database, which means that you can run galileo and pcli concurrently and they won't step on each other.

@plaidfinch plaidfinch merged commit 5eba745 into main Apr 27, 2023
@plaidfinch plaidfinch deleted the try-in-memory-db branch April 27, 2023 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants