Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe example and development dependency declarations update DuckDB versions or constraints. The integration tests use ChangesDuckDB Updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The dependency update and example fallback are compatible with the supported Python versions. No concrete integration failure is established, so no specific merge blocker remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)✅ Passed checks (4 passed)Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
… into chore/unpin-duckdb # Conflicts: # pixi.lock # pyproject.toml
|
@coderabbitai resume |
✅ Action performedReviews resumed and review finished. |
nielspardon
left a comment
There was a problem hiding this comment.
Please regenerate pixi.lock with pixi v0.73.0 or newer (the version CI pins): the merge resolution rewrote it in the older v6 lock format, so pixi lock --check fails and the next pixi command silently rewrites it to v7. Running pixi lock on this branch fixes it and only changes the format.
| conn.execute("CREATE TABLE stores AS SELECT * FROM data") | ||
| conn.execute("CREATE TABLE sales AS SELECT * FROM sales_data") |
There was a problem hiding this comment.
Pass the Arrow tables in explicitly so this doesn't depend on DuckDB finding data by Python variable name:
| conn.execute("CREATE TABLE stores AS SELECT * FROM data") | |
| conn.execute("CREATE TABLE sales AS SELECT * FROM sales_data") | |
| conn.from_arrow(data).create("stores") | |
| conn.from_arrow(sales_data).create("sales") |
| try: | ||
| duckdb.install_extension("substrait") | ||
| except duckdb.duckdb.HTTPException: | ||
| except duckdb.HTTPException: |
There was a problem hiding this comment.
Use .to_arrow_table().schema at examples/duckdb_example.py:34 too, to match the tests (that line isn't in the diff, so no suggestion block).
|
|
||
| [dependency-groups] | ||
| dev = ["pytest >= 7.0.0", "substrait-antlr==0.102.0", "pyyaml", "sqloxide", "deepdiff", "duckdb<=1.2.2; python_version < '3.14'", "datafusion"] | ||
| dev = ["pytest >= 7.0.0", "substrait-antlr==0.102.0", "pyyaml", "sqloxide", "deepdiff", "duckdb", "datafusion"] |
There was a problem hiding this comment.
Would a range like duckdb>=1.5,<1.6 be worth keeping here? The old pin guarded against a lock upgrade landing on a DuckDB release the substrait community extension doesn't support yet.
drops the duckdb version pin from dev dependencies.