-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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](runtime-filter) avoid dcheck fail when rf merge failed #39172
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
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
dataroaring
approved these changes
Aug 9, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
the
approved
Indicates a PR has been approved by one committer.
label
Aug 9, 2024
PR approved by anyone and no changes requested. |
zhiqiang-hhhh
approved these changes
Aug 9, 2024
dataroaring
pushed a commit
that referenced
this pull request
Aug 10, 2024
## Proposed changes avoid dcheck fail when rf merge failed there is a difference in the logic of calculating bf size between 2.1 and 3.0, so the merge will fail this pr is to prevent core dump caused by dcheck failure during rolling upgrade.
wyxxxcat
pushed a commit
to wyxxxcat/doris
that referenced
this pull request
Aug 14, 2024
…e#39172) ## Proposed changes avoid dcheck fail when rf merge failed there is a difference in the logic of calculating bf size between 2.1 and 3.0, so the merge will fail this pr is to prevent core dump caused by dcheck failure during rolling upgrade.
BiteTheDDDDt
added a commit
that referenced
this pull request
Sep 5, 2024
## Proposed changes avoid dcheck fail when rf merge failed there is a difference in the logic of calculating bf size between 2.1 and 3.0, so the merge will fail this pr is to prevent core dump caused by dcheck failure during rolling upgrade.
hello-stephen
pushed a commit
that referenced
this pull request
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by one committer.
dev/2.1.6-merged
dev/3.0.1-merged
doing
reviewed
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.
Proposed changes
avoid dcheck fail when rf merge failed
there is a difference in the logic of calculating bf size between 2.1 and 3.0, so the merge will fail
this pr is to prevent core dump caused by dcheck failure during rolling upgrade.