Skip to content

fix: Optimizes SpillingGrouper for high cardinality dimension(s) GroupBy with large memory footprint aggregators #834

fix: Optimizes SpillingGrouper for high cardinality dimension(s) GroupBy with large memory footprint aggregators

fix: Optimizes SpillingGrouper for high cardinality dimension(s) GroupBy with large memory footprint aggregators #834

Triggered via pull request April 21, 2026 22:42
Status Failure
Total duration 6s
Artifacts

pr-checks.yml

on: pull_request
Verify PR title conforms to Conventional Commits
3s
Verify PR title conforms to Conventional Commits
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Verify PR title conforms to Conventional Commits
No release type found in pull request title "Optimizes SpillingGrouper for high cardinality group by dimensions with large memory footprint aggregators". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/ Available types: - backport - build - ci - dev - docs - feat - fix - minor - perf - refactor - release - revert - style - test
Verify PR title conforms to Conventional Commits
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: amannn/action-semantic-pull-request@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/