feat: billing dry run #342
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
alanshaw
requested review from
Gozala,
travis and
vasco-santos
and removed request for
Gozala
View stack outputs
|
vasco-santos
approved these changes
Mar 13, 2024
| * @template T | ||
| * @returns {import('../lib/api.js').StorePutter<T> & import('../lib/api.js').StoreLister<any, T> & import('../lib/api.js').StoreGetter<any, T>} | ||
| */ | ||
| export const createMemoryStore = () => { |
There was a problem hiding this comment.
I assume based on your ran that it does not load a lot of memory in the host running. wondering if we should write in disk to avoid getting out of memory, but probably nothing close to happen that we can start with in memory?
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.
A script to do dry run of the billing pipeline. It reads production data, but does not write to any production tables.