Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Release][C++] C++ Extra workflow for the `apache-arrow-24.0.0-rc0` was canceled

Open Beginner friendly
#49,749 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd, release

Research direction

Start with .github/workflows/cpp_extra.yml at lines 77-79, then inspect the C++ Extra ODBC job around lines 735-767 and the linked workflow runs. Determine how concurrency treats the release branch push and tag push when they share a commit. Done means the tag-triggered job is no longer canceled by the branch-triggered workflow.

Written by the indexing model from the issue text.

Description

Component: C++ Component: Release Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

C++ Extra includes the ODBC build and it will upload built ODBC artifacts when a tag is pushed:

https://github.com/apache/arrow/blob/4eca50770f7f2c5938a676f0719fbfc8aae4803c/.github/workflows/cpp_extra.yml#L735-L767

But the job for the apache-arrow-24.0.0-rc0 was canceled:

https://github.com/apache/arrow/actions/runs/24404382907

Because the push to the release-24.0.0-rc0 branch includes the same commit as the apache-arrow-24.0.0-rc0 and we have concurrency.group:

https://github.com/apache/arrow/actions/runs/24404394663

https://github.com/apache/arrow/blob/4eca50770f7f2c5938a676f0719fbfc8aae4803c/.github/workflows/cpp_extra.yml#L77-L79

We don't want to cancel the job triggered by tag push. Can we improve the current concurrency.group?

Component(s)

Release, C++

Dominant language
C++
Stars
17.1k
Forks
4.3k
Avg merge
4d 5h
Merged PRs (30d)
94

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow

All issues in apache/arrow

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.