Skip to content

Fix DuckDB main canary parser compatibility - #53

Open
nicosuave wants to merge 1 commit into
mainfrom
fix-canary-ci
Open

nicosuave wants to merge 1 commit into
mainfrom
fix-canary-ci

Conversation

@nicosuave

Copy link
Copy Markdown
Member

DuckDB main made ParseResult::offset and length private, breaking the scheduled canary build in frontend_peg.cpp. Use the public GetLocation() API for syntax spans, modifier dimensions, measure declarations, and CURRENT references. The same API is available in the supported DuckDB 2.0 release.

Validation: compiled the changed translation unit against DuckDB v2.0.0 (d54cbbe3df17) and current main (77b845c7b5a); git diff --check passed. The release pipeline and DuckDB-main canary will validate the complete builds and SQL suites on this branch.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T16:17:59.947685Z d8e460b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant