andygrove commented on issue #5454: URL: https://github.com/apache/datafusion-comet/issues/5454#issuecomment-5432471525
All 28 recommended label sets from this pass have now been applied with a token that has write access, so the *Failed to label* section above is resolved. I re-checked every issue first: all 28 were still open and still carried `requires-triage`, and none had been re-triaged in the interim, so the recommendations were applied verbatim with no adjustments. Applied: - `bug` + `priority:critical` + `area:aggregation` — #5419, #5418 - `bug` + `priority:critical` + `area:expressions` — #5401 - `bug` + `priority:low` — #5389 - `enhancement` + the recommended area labels — #5448, #5447, #5446, #5438, #5437, #5436, #5435, #5434, #5433, #5432, #5431, #5430, #5429, #5428, #5427, #5426, #5425, #5424, #5413, #5411, #5397, #5396, #5390, #5386 `requires-triage` was removed from all 28. Verified afterwards that each issue carries exactly one of `bug`/`enhancement`, that priority labels appear only on the four bugs, and that pre-existing labels not in the guide's table (`correctness` and `array expressions` on #5401, `test`/`performance`/`EPIC` on #5396, `area:udf` on #5386) were left untouched. Still carrying `requires-triage`, and intentionally not labeled: this issue and the three earlier triage summaries #5385, #5325, #5231. Those are process/meta artifacts for a reviewer to spot-check and close, matching how #5052 and earlier were handled. Two things in the notes above are worth a maintainer's eye rather than being settled by the labels: the #5447-vs-#5382 classification (`enhancement` here, whereas #5382 was labeled `bug` + `priority:medium`), and the label-vocabulary gaps — the guide lists `spark 4` but the repo only has `spark 4.0`/`4.1`/`4.2`, and `area:udf` exists in the repo but not in the guide's area table, which is why #5386, #5437, #5447, and #5389 ended up with thin or empty area lists. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
