jbbqqf commented on PR #30658:
URL: https://github.com/apache/airflow/pull/30658#issuecomment-1528789111

   > To start - maybe get all the tests succeed :D (they are failing currently)?
   Touché :wink: 
   
   @potiuk  Actually when I posted my comment, CI was all green and I thought 
for a moment I had solved the issue. As I can see it takes time so that all 
pipelines finish.
   
   I tried to run those tests with breeze but I can't manage to find the 
appropriate command that would specifically target the modified operators 
(running static checks with breeze is OK though). Can you suggest arguments I 
should pass to this tool to understand locally what's going on ? (CI failures 
don't seem to output verbose enough logs)
   
   > And the second thing -> wait for a maintainer to merge it. And sometimes 
be patient with it @jbbqqf. Yes it takes sometimes a number of passes, multiple 
builds, conflict resolving and sometimes even few positive reviews to pass.
   > 
   > All that so that your change will be good, reviewed, tested, and being 
ready for anyone else to take over and develop further. Yes it can be annoying 
but if you consider that you might disappear tomorrow and there are a number of 
people here who will take over the maintenance of the code with confidence.
   > 
   > I hope you understand all that.
   Sure :+1: 
   
   I read in Airflow's contributing guide that being pushy with maintainers was 
interpreted well, as a sign of interest. This was my intent. I will be patient 
as long as necessary.
   
   I appreciate your efforts to demonstrate diplomacy.
   
   Reference:
   
   https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst
   
   > Ping @ #development slack, comment @people. Be annoying. Be considerate.
   
   > It's your responsibility as an author to ping committers to review your PR 
- be mildly annoying sometimes, it's OK to be slightly annoying with your 
change - it is also a sign for committers that you care


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