Feature: Allow 512 GB persistant volume #629
Open
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
1yam
changed the title
1yam
changed the title
|
aleph-messages is now using pydantic V2. |
1yam
force-pushed
the
1yam-persistant-upgrade
branch
from
a2ceb2b
to
1e8d54a
Compare
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.
Explain what problem this PR is resolving
Related Clickup or Jira tickets : ALEPH-42
Self proofreading checklist
Changes
Using aleph-message branch to allow message being processed (will need to change to new version when published)
And new test.
How to test
Just launch vm with more than 100 GiB on persistent storage
Notes
Would need to do end to end testing to ensure CRN working well with larger disk (but should be the case)