bbovenzi commented on PR #46827:
URL: https://github.com/apache/airflow/pull/46827#issuecomment-2664193589

   > This is failing it's static check and I don't know how to decipher the 
error:
   > 
   > ```
   > 
/Users/ash/code/airflow/airflow/airflow/ui/src/pages/TaskInstance/Logs/Logs.tsx
   >    97:21  error  Unsafe assignment of an error typed value  
@typescript-eslint/no-unsafe-assignment
   >   122:27  error  Unsafe assignment of an error typed value  
@typescript-eslint/no-unsafe-assignment
   > 
   > /Users/ash/code/airflow/airflow/airflow/ui/src/queries/useLogs.tsx
   >   43:59  error  Unsafe call of an `error` type typed value             
@typescript-eslint/no-unsafe-call
   >   50:7   error  Unexpected use of continue statement                   
no-continue
   >   60:18  error  Unsafe assignment of an `any` value                    
@typescript-eslint/no-unsafe-assignment
   >   75:5   error  Unsafe assignment of an error typed value              
@typescript-eslint/no-unsafe-assignment
   >   75:19  error  Unsafe call of an `error` type typed value             
@typescript-eslint/no-unsafe-call
   >   75:24  error  Unsafe member access .map on an `error` typed value    
@typescript-eslint/no-unsafe-member-access
   >   78:41  error  Invalid type "unknown" of template literal expression  
@typescript-eslint/restrict-template-expressions
   >   81:14  error  Unsafe assignment of an error typed value              
@typescript-eslint/no-unsafe-assignment
   >   86:5   error  Unsafe assignment of an error typed value              
@typescript-eslint/no-unsafe-assignment
   > ```
   
   
   It's a bunch of typescript issues. Usually easier to read inline. We we 
weren't setting the types of the log parsing functions so that made typescript 
say every variable assignment in the function was unsafe.


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