You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tooling.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2026/07/08 19:49:27 UTC

[I] No obvious way how to resolve concerns (tooling-releases-client)

potiuk opened a new issue, #31:
URL: https://github.com/apache/tooling-releases-client/issues/31

   We have some concerns raised when preparing the release - https://release-test.apache.org/report/magpie/0.1.0/apache-magpie-0.1.0-source.zip
   
   The concern is about missing licence flles  - but those are false negatives (see https://github.com/apache/tooling-trusted-releases/issues/1380 and https://github.com/apache/tooling-trusted-releases/issues/1379) - so we would like to start vote anyway.
   
   When I attempt to start a vote I got this message:
   
   ```
   atr vote start magpie 0.1.0 00008  \
     -m dev@magpie.apache.org --duration 72 \
     --subject "[VOTE] Release Apache Magpie 0.1.0 from 0.1.0-rc1"
   atr: error: Error message from the API:
   409 https://release-test.apache.org/api/vote/start
   {"error":"Review and acknowledge every current concern group before starting the vote: License Headers","request_id":"112219a0-4465-4d55-8978-c425b9a0d7b4"}
   ```
   
   But it's not clear how to review and acknowledge the concerns. 
   
   
   Atr vote does not have any command:
   
   ```
   ⏚ [jarekpotiuk:~/code/magpie] main+ ± atr vote
   Usage: atr vote COMMAND
   
   Vote operations.
   
   ╭─ Commands ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
   │ resolve   Resolve a vote.                                                                                                                     │
   │ start     Start a vote.                                                                                                                       │
   │ tabulate  Tabulate a vote.                                                                                                                    │
   ╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
   ```
   
   The web UI only allows to "hide" concerns - but not resolve them.\
   
   I could not find any other CLI or too to resolve the concerns.
   
   


-- 
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: issues-unsubscribe@tooling.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] No obvious way how to resolve concerns (tooling-releases-client)

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #31:
URL: https://github.com/apache/tooling-releases-client/issues/31#issuecomment-4918658635

   There is something about "--concerns-noted" and I tried to do this:
   
   
   ```
   atr vote start magpie 0.1.0 00008 \
     -m dev@magpie.apache.org -d 72 \
     -s "[VOTE] Release Apache Magpie 0.1.0 from 0.1.0-rc1" \
     --concerns-noted \
     "Note: ATR's license-header check flags one header-less shell script (run.sh) that the project's own RAT config (.rat-excludes) intentionally excludes; the repo rat CI gate is clean. Acknowledged."
   ```
   
   But it did not work:
   
   ```
   409 https://release-test.apache.org/api/vote/start
   {"error":"Review and acknowledge every current concern group before starting the vote: License Headers","request_id":"eab1d579-fe7b-4859-bc2b-315ea2863009"}
   ```
   
   


-- 
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: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] No obvious way how to resolve concerns (tooling-releases-client)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #31:
URL: https://github.com/apache/tooling-releases-client/issues/31#issuecomment-4926378770

   The expected format is a comma separated list of concern keys, e.g. `--concerns-noted atr.tasks.checks.license.headers`, which was undocumented. The concern keys themselves were also undiscoverable from the client, so I fixed both problems by documenting the format and adding the concern keys to `atr check concerns`.
   
   Resolved by a1b056204fd55463514ce75fa9af7e3a8a817073. Thanks for the report!
   


-- 
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: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] No obvious way how to resolve concerns (tooling-releases-client)

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #31:
URL: https://github.com/apache/tooling-releases-client/issues/31#issuecomment-4926446221

   Thanks! 


-- 
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: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] No obvious way how to resolve concerns (tooling-releases-client)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp closed issue #31: No obvious way how to resolve concerns
URL: https://github.com/apache/tooling-releases-client/issues/31


-- 
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: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org