Fix Subtraction overflow in max_distinct_count when hash join has a pushed-down limit
#61098
alambrust.yml
on: pull_request
linux build test
1m 39s
build and run with wasm-pack
5m 17s
cargo test (macos-aarch64)
10m 21s
Verify Vendored Code
1m 14s
Check cargo fmt
1m 15s
Verify MSRV (Min Supported Rust Version)
5m 9s
cargo check datafusion-common features
2m 4s
cargo check datafusion-substrait features
3m 53s
cargo check datafusion-proto features
2m 32s
cargo check datafusion features
5m 55s
cargo check datafusion-functions features
2m 48s
cargo test (amd64)
3m 8s
cargo test datafusion-cli (amd64)
1m 54s
cargo examples (amd64)
2m 44s
cargo test doc (amd64)
3m 14s
cargo doc
1m 55s
verify benchmark results (amd64)
4m 22s
Run sqllogictest with Postgres runner
2m 47s
Run sqllogictest in Substrait round-trip mode
2m 39s
clippy
1m 51s
check Cargo.toml formatting
3m 14s
check configs.md and ***_functions.md is up-to-date
2m 12s
check example README is up-to-date
4m 46s
Annotations
14 warnings
|
linux build test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo test datafusion-cli (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo doc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
check configs.md and ***_functions.md is up-to-date
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo check datafusion-proto features
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run sqllogictest in Substrait round-trip mode
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo examples (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run sqllogictest with Postgres runner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo test (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo test doc (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
verify benchmark results (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo check datafusion features
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: runs-on/action@cd2b598b0515d39d78c38a02d529db87d2196d1e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
cargo test (macos-aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@f13886b937689c021905a6b90929199931d60db1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|