ashb opened a new pull request #10862:
URL: https://github.com/apache/airflow/pull/10862


   The SmartSensor PR #5499 introduces slightly different behaviour 
onlist_py_files happens when given a file path directly.
   
   Prior to that PR, if given a file path it would not include examples.
   
   After that PR was merged, it would return that path and the example dags
   (assuming they were enabled.)
   
   @potiuk I'm not sure what behaviour you were seeing that caused you to 
quarantine it, but for me _every_ time I ran this test on SQLite it failed. 
(well hung for ever.) This PR fixes that.
   
   Please let me know if you quarantined it for a different reason, and I can 
leave it quarantined.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to