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

   ### Apache Airflow version
   
   Other Airflow 2/3 version (please specify below)
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   3.1.1
   
   ### What happened?
   
   I am using a custom class that extends `CloudRunExecuteJobOperator` and 
overrides the `pre_execute` and `execute` functions. Among other things, these 
functions produce logs. 
   
   When running the DAG with that class and `deferrable=True` those logs 
briefly appear in the UI. Then they disappear, only to re-appear when the 
status is no longer `deferred`. 
   
   Sounds similar to this one https://github.com/apache/airflow/issues/28647, 
but that issue is pretty old...
   
   ### What you think should happen instead?
   
   I should be seeing all logs all the time, regardless of the tasks status.
   
   Since I am pretty sure this is related to `deferred` maybe there is also 
another proper way to see the logs, or a workaround for this?
   
   ### How to reproduce
   
   Use this in a DAG:
   
   ```
   class CustomCloudRunJobOperator(CloudRunExecuteJobOperator):
       def pre_execute(self, context: Context) -> None:
           self.log.info("Some log here")
           super().pre_execute(context)
   ```
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### 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