yzhangyext opened a new issue, #64066:
URL: https://github.com/apache/airflow/issues/64066

   ### Apache Airflow version
   
   Other Airflow 3 version (please specify below)
   
   ### If "Other Airflow 3 version" selected, which one?
   
   3.1.7
   
   ### What happened?
   
   airflowctl dagrun list does not appear to honor the --limit flag correctly, 
but rather, it returns 8 times the number of results.
   
   For example:
   
   --limit=1 returns 8 dag runs
   --limit=2 returns 16 dag runs
   --limit=10 returns 80 dag runs
   
   The extra results are distinct dag runs, so this does not appear to be a 
duplicate-printing or output-formatting issue.
   
   The Airflow REST API returns the correct number of results for the 
equivalent request, which suggests the issue is in airflowctl rather than the 
Airflow backend.
   
   ### What you think should happen instead?
   
   airflowctl dagrun list --limit=N should return at most N dag runs.
   
   ### How to reproduce
   
   airflowctl version
   {'airflowctl_version': '0.1.3'}
   
   airflowctl dagrun list --dag-id=xxx --limit=1 --state=success
   airflowctl dagrun list --dag-id=xxx --limit=2 --state=success
   airflowctl dagrun list --dag-id=xxx --limit=10 --state=success
   
   ### Operating System
   
   MacOS 15.4.1
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to