1fanwang commented on PR #71763:
URL: https://github.com/apache/airflow/pull/71763#issuecomment-5881029765
Confirmed the blocker against a real cluster rather than a stand-in, since
my first pass used a local copy of the route signature.
```
$ curl -s -o /dev/null -w '%{http_code}\n'
.../taskInstances/t/logs/1?map_index=-1
404
$ curl -s ... /taskInstances/t/logs/-1?map_index=-1
422 {"detail":[{"type":"greater_than_equal","loc":["path","try_number"],
"msg":"Input should be greater than or equal to
0","input":"-1","ctx":{"ge":0}}]}
```
The `404` on the first call is the useful half: the path and auth are
correct and the handler ran, so the `422` is the endpoint rejecting
`try_number` itself rather than a routing miss. The suggestion on
`ARG_TRY_NUMBER` applies unchanged.
One retraction: I asked for a newsfragment, and that was wrong. There is no
`newsfragments` directory under `airflow-ctl/`, so this does not take one.
Sorry for the detour.
--
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]
