Conversation
see MaterializeInc/materialize#32629 needed to make sure Cargo Release builds don't run into MaterializeInc/database-issues#9313
def-
force-pushed
the
pr-always-assert
branch
from
4ebbcd8 to
45a2a34
Compare
def-
added a commit
to def-/materialize
that referenced
this pull request
Oct 23, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
see MaterializeInc/materialize#32629
needed to make sure Cargo Release builds don't run into https://github.com/MaterializeInc/database-issues/issues/9313
Cargo always does RelWithDebInfo builds in cmake by default, with Bazel we had Release builds.