-
Notifications
You must be signed in to change notification settings - Fork 57
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
chore(rln): rln message limit to 100 #2883
Merged
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
Contributor
alrevuelta
commented
Jul 5, 2024
- Set rln message limit to 100
You can find the image built from this PR at
Built from 12c499a |
alrevuelta
changed the title
Set rln message limit to 100
chore(rln): rln message limit to 100
Jul 5, 2024
This PR may contain changes to database schema of one of the drivers. If you are introducing any changes to the schema, make sure the upgrade from the latest release to this change passes without any errors/issues. Please make sure the label |
alrevuelta
force-pushed
the
change-rln-limit
branch
from
July 8, 2024 09:00
2d35952
to
e6e364f
Compare
alrevuelta
requested review from
rymnc,
jm-clius,
fryorcraken and
Ivansete-status
July 8, 2024 09:01
Ivansete-status
approved these changes
Jul 8, 2024
rymnc
approved these changes
Jul 8, 2024
alrevuelta
added a commit
that referenced
this pull request
Jul 8, 2024
This reverts commit d3292bc.
This was referenced Jul 8, 2024
Ivansete-status
pushed a commit
that referenced
this pull request
Jul 15, 2024
Ivansete-status
pushed a commit
that referenced
this pull request
Jul 15, 2024
Ivansete-status
pushed a commit
that referenced
this pull request
Jul 15, 2024
Ivansete-status
added a commit
that referenced
this pull request
Jul 15, 2024
* chore(rln): rln message limit to 100 (#2883) * postgres_driver: add more error handling when creating partitions Given that multiple nodes can be connected to the same database, it can happen that other node did something that my node was willing to do. In this commit, we overcome the possible "interleaved" partition creation. --------- Co-authored-by: Alvaro Revuelta <[email protected]>
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.