Skip to content

optimizer: Downgrade repr type error: base_eq failed for to trace#35050

Merged
def- merged 1 commit intoMaterializeInc:mainfrom
def-:pr-downgrade-base-eq-error
Feb 17, 2026
Merged

optimizer: Downgrade repr type error: base_eq failed for to trace#35050
def- merged 1 commit intoMaterializeInc:mainfrom
def-:pr-downgrade-base-eq-error

Conversation

@def-
Copy link
Contributor

@def- def- commented Feb 17, 2026

@def- def- requested review from ggevay and mgree February 17, 2026 13:17
@def- def- requested a review from a team as a code owner February 17, 2026 13:17
@def- def- added the release-blocker Critical issue that should block *any* release if not fixed label Feb 17, 2026
@github-actions
Copy link

Pre-merge checklist

  • The PR title is descriptive and will make sense in the git log.
  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).

Copy link
Contributor

@ggevay ggevay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-blocker Critical issue that should block *any* release if not fixed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants