github-actions[bot] opened a new pull request, #73331: URL: https://github.com/apache/airflow/pull/73331
airflowctl funnels every command through a single handler whose job is to turn a failure into one line the operator can act on. That handler only recognised ServerResponseError, which the API client builds solely for 4xx/5xx responses carrying a JSON body -- everything else leaves the response hook raising the bare httpx.HTTPStatusError that ServerResponseError subclasses, so no clause caught it. The responses that fall outside that narrow definition are precisely the ones an operator has least context for: an SSO proxy answering with a redirect, or an ingress returning its own HTML error page. Those never reached the Airflow API server at all, and a traceback tells the operator nothing about why. (cherry picked from commit 44094b2661b7f90d3cb0f53d1a43a457bb38a979) Co-authored-by: Y-C <[email protected]> -- 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]
