| chore: update bug report template (#5652) ## Changes Made I more often than not found myself checking "Other" as many of the categories are not super relevant. So i just updated them based off analyzing some of the recent issues to find the most popular categories. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> ## Checklist - [ ] Documented in API Docs (if applicable) - [ ] Documented in User Guide (if applicable) - [ ] If adding a new documentation page, doc is added to docs/mkdocs.yml navigation - [ ] Documentation builds and is formatted properly --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> | 10 个月前 |
| fix(ci): use content-hash mtimes to prevent stale cargo cache artifacts (#6546) The restore-mtime action was causing CI builds to use stale cached cargo artifacts, leading to compilation errors like no variant or associated item named 'RandomShuffle' found for enum 'NodeType' on PR #6481. Cargo checks freshness by asking "is any source file newer than my invoked.timestamp?" The old restore-mtime set source files to their git commit timestamps, which are always in the past relative to the cached invoked.timestamp (whose mtime is the build time that created the cache). So both unchanged AND changed files looked "older" than the cached artifacts, and cargo never triggered rebuilds - even when file content differed between the cache-save build and the current checkout. To fix this, restore-mtime now uses content hashing instead of git timestamps. It hashes all source files via sha256sum and compares against saved hashes from the previous cache build (stored in target/.source-hashes, included in the Swatinem/rust-cache archive automatically). Unchanged files (same hash) get a fixed past timestamp (2020-01-01), guaranteed older than any invoked.timestamp. Changed files keep the checkout mtime ("now"), guaranteed newer. This gives cargo the correct signal for both cases. Also purged the existing GitHub Actions Rust build caches to clear stale artifacts. --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> | 6 个月前 |
| chore: Drop Python 3.9 (#5479) ## Changes Made Python 3.9 is EOL starting from Nov 1, so lets drop it and make 3.10 the minimum. Also, start testing ranges 3.10 to 3.13 --------- Co-authored-by: Colin Ho <colin.ho99@gmail.com> | 10 个月前 |
| feat: add Flight shuffle to Flotilla (#6123) Add support for peer-to-peer network transfers for shuffles using the Arrow Flight protocol in the distributed runner. Follow ups: * Add testing infrastructure for distributed TPCH with and without flight shuffle * Support pre-shuffle merge with flight * Refactor Ray-based shuffles to be structured more like Flight * Make shuffle interface more generic | 7 个月前 |
| | 6 个月前 |
| chore: Update codeowners (#6183) ## Changes Made <!-- Describe what changes were made and why. Include implementation details if necessary. --> ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> | 7 个月前 |
| fix: Dependabot tweaks (#4659) | 1 年前 |
| chore: remove checklist from pr template (#5653) ## Changes Made nobody is using the checklist. so lets just remove it. ## Related Issues <!-- Link to related GitHub issues, e.g., "Closes #123" --> | 10 个月前 |
| ci(release-drafter): use conventional commit labels (#3503) | 1 年前 |