potiuk commented on PR #22998:
URL: https://github.com/apache/airflow/pull/22998#issuecomment-1098889991

   > * Breeze in CI should always be installed in the environment, why we 
should validate the installation for CI?
   
   Yeah. It **should**. But it already turned out that it's not always is. See 
the conversation here: https://github.com/apache/airflow/pull/22961 . We really 
want people who are not familiar with breeze and CI got precise information 
about what is wrong. They (even @kaxil !) cannot easily figure out what's wrong 
when they see a cryptic stack-trace - mostly because they do not have the 
context. The CI is a living system that changes continuously and we can add new 
jobs in the future or mistakenly remove stuff. Having a nice message explaining 
what's wrong AND telling the user what to do is way better than cryptic stack 
trace.
   
   > * One thing I notices is that we don't have instructions to "uninstall 
breeze" in case the developer wanted to do it.
   
   Very, very food point - can you add it please (separate PR) :) ? It could be 
added in the cheatsheeet as well as in the BREEZE.rst. 


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to