bugraoz93 commented on PR #55912:
URL: https://github.com/apache/airflow/pull/55912#issuecomment-3382071010

   > ```
   > root@6d9aca209fd4:/opt/airflow# airflowctl variables list
   > Please enter password for encrypted keyring:
   > Limit: None
   > 2025-10-06 03:57:08 [warning  ] Server error                   
[airflowctl.api.client] extra={'detail': [{'type': 'int_parsing', 'loc': 
['query', 'limit'], 'msg': 'Input should be a valid integer, unable to parse 
string as an integer', 'input': ''}]}
   > Server response error: Client error message: {'detail':
   > [{'type': 'int_parsing', 'loc': ['query', 'limit'],
   > 'msg': 'Input should be a valid integer, unable to parse
   > string as an integer', 'input': ''}]}
   > Client error,  Please check the command and its
   > parameters. If you need help, run the command with
   > --help.
   > ```
   > 
   > ```
   > limit: int | None = 50,
   >         params: dict | None = None,
   >     ) -> T | ServerResponseError:
   >         limit_flag = True if limit is not None else False
   >         print(f"Limit: {limit}")
   >         if params is None:
   >             params = {"limit": limit}
   > ```
   >             
   >  ```
   >  def list(self,limit:int) -> VariableCollectionResponse | 
ServerResponseError:
   >         """List all variables."""
   >         return super().execute_list(path="variables", 
data_model=VariableCollectionResponse,limit=limit)
   > ```
   > 
   > @bugraoz93, Sorry I didn’t understand that we were trying to pass it as a 
function argument. 
   > Now I’m getting the same error message
   > 
   >            
   >  
   
   Thanks for checking @Prab-27! This is exactly why I followed that ugly 
approach rather than making it the default in the method definition. We can 
find and fix this at a later stage and keep it like this for a while
   


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