| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[RUST] Migrate hypothesis sort tests (#782) Migrates our hypothesis sort tests which required certain fixes in our kernels. -- Fixes: 1. Add filter kernel for BinaryArray and use with_match_physical_daft_types for dispatch 2. Add size_bytes for BinaryArray and use with_match_physical_daft_types for dispatch 3. Use with_match_daft_types in Series::empty for dispatch 4. Use with_match_physical_daft_types in Series::head for dispatch --------- Co-authored-by: Jay Chia <jaychia94@gmail.com@users.noreply.github.com> | 3 年前 | |
test: Filter null bytes from generated column names in property-based tests (#6213) ## Summary - Filters embedded null bytes ( \0) from Hypothesis-generated column names in property-based tests - Fixes a panic in arrow-rs FFI layer (FFI_ArrowSchema::with_name calls CString::new(name).unwrap()) triggered when Ray serializes columns with null bytes in their names - The failing CI run: https://github.com/Eventual-Inc/Daft/actions/runs/22042235355 ## Root Cause The Hypothesis text() strategy can generate strings containing null bytes. When such a string is used as a column name and the test runs on the Ray runner, the serialization path (Series.__reduce__ → to_arrow() → Arrow C Data Interface) hits a panic in arrow-rs v57.2.0 at arrow-schema/src/ffi.rs:165: rust // FFI_ArrowSchema::with_name() - panics instead of returning error self.name = CString::new(name).unwrap().into_raw(); Null bytes in column names are inherently invalid for the Arrow C Data Interface (which uses null-terminated C strings), so filtering them from generated test data is the correct fix. The upstream arrow-rs bug (.unwrap() instead of error propagation) still exists in v57.3.0. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> | 7 个月前 | |
chore: bump mypy and ruff in pre-commit (#5836) ## Changes Made Bump mypy to 1.19.1 and ruff to 0.14.10 and resolve pre-commit errors. Rationale: my local ruff version is much higher than that in the project pre-commit, so I am getting a lot of linter warnings in my IDE. It is also about time to upgrade lints to utilize newer Python language features. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> | 9 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 7 个月前 | ||
| 9 个月前 |