You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are we using the "awaiting ..." labels? If we don't use the "awaiting ..." labels, how about removing them? If we remove them, we can avoid this timing sensitive problem.
#50125 (comment) (you added CI: Extra: C++ and CI: Extra: R) happened on 2026-06-08T14:02:30Z and #50125 (comment) (Archery added awaiting review and removed CI: Extra: C++) happened on 2026-06-08T14:02:40Z.
In Arrow's labeler.yml, CI: Extra: C++ is configured as a labeler-managed label. PR #50125 modified Docker and compose files, which do not match the configured rules for that label. As a result, when labeler ran with sync-labels: true, it removed CI: Extra: C++ as expected.
It looks like the AI is right. @kou Do we need to add more paths to labeler.yml? Or should we perhaps make the "Extra" labels entirely manual (non-automated)?
I'd personally remove them from the labeler.yml and make the extra labels completely manual. I don't think trying to be smart adding them automatically is that useful and I personally trigger them when I think a PR requires those jobs to be executed. Similar to how we trigger crossbow jobs basically.
Activity
pitrou commentedon Jun 9, 2026
@kou
kou commentedon Jun 9, 2026
Could you share a sample PR that the problem happened?
kou commentedon Jun 10, 2026
#50125 (comment) ?
kou commentedon Jun 10, 2026
@raulcd It seems that
arrow/dev/archery/archery/bot.py
Lines 214 to 216 in 9265a71
Are we using the "awaiting ..." labels? If we don't use the "awaiting ..." labels, how about removing them? If we remove them, we can avoid this timing sensitive problem.
pitrou commentedon Jun 10, 2026
I've just used the "Add labels to an issue" API as instructed here to add the Java label to this issue, it didn't remove other labels.
pitrou commentedon Jun 10, 2026
Note that "Add labels to an issue" uses POST while "Set labels for an issue" uses PUT.
pitrou commentedon Jun 10, 2026
The GHA-based issue bot uses
setLabelsinstead ofaddLabelsorremoveLabeland that might be the issue.kou commentedon Jun 10, 2026
#50125 (comment) is a problem case, right?
It's a PR. Our issue bot isn't executed for PR:
arrow/.github/workflows/issue_bot.yml
Lines 20 to 23 in 4e25461
#50125 (comment) (you added
CI: Extra: C++andCI: Extra: R) happened on 2026-06-08T14:02:30Z and#50125 (comment) (Archery added
awaiting reviewand removedCI: Extra: C++) happened on 2026-06-08T14:02:40Z.I think that this timeline is related...
pitrou commentedon Jun 10, 2026
Yes. It happens to me often actually.
Hmm. I see.
It is. But it's weird because
add_labelsis not supposed to remove existing labels...pitrou commentedon Jun 10, 2026
I think the problem is that we're using https://github.com/actions/labeler for PRs which uses
setLabels.Another project had the same problem with it: flutter/flutter#128440
pitrou commentedon Jun 10, 2026
Also see actions/labeler#763 . They claim the issue is fixed but I don't understand how.
pitrou commentedon Jun 25, 2026
Ok, the AI upstream said this:
It looks like the AI is right. @kou Do we need to add more paths to
labeler.yml? Or should we perhaps make the "Extra" labels entirely manual (non-automated)?raulcd commentedon Jun 25, 2026
I'd personally remove them from the
labeler.ymland make the extra labels completely manual. I don't think trying to be smart adding them automatically is that useful and I personally trigger them when I think a PR requires those jobs to be executed. Similar to how we trigger crossbow jobs basically.kou commentedon Jun 25, 2026
I think that the answer isn't right.
The labelar job is executed when PR is opened or synchronized (pushed):
arrow/.github/workflows/dev_pr.yml
Lines 20 to 30 in cffe22d
arrow/.github/workflows/dev_pr.yml
Lines 86 to 94 in cffe22d
The
CI: Extra: C++label isn't removed after you set it manually again #50125 (comment) and then you pushed to the branch again #50125 (comment) .If the answer is right, the
CI: Extra: C++label should be removed when you pushed to the branch again. But theCI: Extra: C++label wasn't removed.apacheGH-50133: [CI] Make extra labels entirely manual
GH-50133: [CI] Make extra labels entirely manual on PRs (#50256)
raulcd commentedon Jun 30, 2026
Issue resolved by pull request 50256
#50256