You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/11/13 23:18:33 UTC
[GitHub] [airflow] barskern opened a new issue #19578: Custom timetable causes crash using airflow test
barskern opened a new issue #19578:
URL: https://github.com/apache/airflow/issues/19578
### Apache Airflow version
2.2.1 (latest released)
### Operating System
Arch Linux
### Versions of Apache Airflow Providers
None relevant
### Deployment
Virtualenv installation
### Deployment details
A local installation for development purposes.
### What happened
Following the tutorial for custom timetable (https://airflow.apache.org/docs/apache-airflow/stable/howto/timetable.html) causes a error when the dag is run using `airflow tasks test example_after_workday_timetable_dag 2021-11-14`.
### What you expected to happen
I expected it to work.
### How to reproduce
Run the code from the tutorial, e.g.:
```python
from airflow.decorators import dag, task
from airflow.example_dags.plugins.workday import AfterWorkdayTimetable
@dag(
start_date=datetime(2020, 1, 1),
timetable=AfterWorkdayTimetable(),
)
def example_etl():
@task()
def extract():
pass
extract()
example_etl_dag = example_etl()
```
### Anything else
_No response_
### Are you willing to submit PR?
- [X] 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: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974681030
Oh! I misread then, and identified the problem wrong. But the root issue is somewhat similar though. In both cases, the command would find an existing DAG run, and re-run either one ti or all tis in it.
The problem is that, if a DAG run was created before the timetable was changed, the run will not be able to infer a meaningful data interval. Before 2.2, a DAG run only has `execution_date`, and the data interval needs to be inferred, but _the inferring logic should be based on the previous schedule definition_ because that’s what scheduled that run, but that schedule no longer exists. Furthermore, a custom timetable is not capable of inferring a data interval from a logical date, because there’s no such interface on the timetable right now, and that’s due to this idea not making logical sense in the first place—a DAG run’s logical date and data interval are conceptually independent.
So unless we change the semantic for `dags test` and `tasks test` (which is not trivial), we either need to “invent” something to tie logical date to data interval and give up their independency (with long term consequences), or we need to…give up, in a sense. When we hit the situation, we can show a friendly-ish message explaining how this does not work (the run you’re trying to trigger was created before Airflow 2.2 and is not compatible with custom timetables), and provide a solution for the user to get out of this. The easiest solution would be to simply delete that run and re-trigger it on Airflow 2.2, or we could potentially provide a script for the user to “migrate” that existing run to 2.2.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974683249
What still worries me - why we have the `infer_data_interval` documented but not used @uranusjr :) ?
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] boring-cyborg[bot] commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-968173598
Thanks for opening your first issue here! Be sure to follow the issue template!
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974679199
But this case is `airflow tasks test` not the `airlfow dag tests` (and I do agree dag tests is not good).
For `tasks test` I think the data interval should be inferred as in the docs, and regardles from the error reported with task tests I think `infer_data_interval` not being called at all in our code is quite a bit worrying.
(But this is my first closer look at the timetable implementaion so I might have missed something)
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974675081
Hmm @uranusjr - maybe I am missing something but I believe we simply did not plug calling `infer_data_interval` from custom timetables. I cannot find a single place where it would be called, and I believe it should be used for Custom Timetables to infer the interval for manual/test/out-of-bands runs.
I believe we simply lost it while implementation - even if it is nicely described in the docs. :)
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] vaci commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
vaci commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974654209
I see a similar issue when attempting to run a task using a custom Timetable, as it is then not possible to render templates in an operator.
The problem is caused by this code, which specifically checks for certain sub-classes of Timetable:
https://github.com/apache/airflow/blob/2.2.1/airflow/models/dag.py#L652
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974674332
Is this an entirely new DAG, or are you changing an existing DAG to use a custom timetable?
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974684561
Yeah. yeah I understand that - but it doesn't seem to be used in the code AT ALL (or maybe I missed it when searching). I just could not find a single call to the `infer_data_interval` in the whole Airflow codebase. As far as I can see it is only mentioned in the Custom Timetable example.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974684561
Yeah. yeah I understand that - but it doesn't seem to be used in the code AT ALL (or maybe I missed it when searching). I just could not find a single call to the `infer_data_interval` in the whole Airflow codebase.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974683139
> Why don't we add `data-interval` to `dags test` and `tasks tests` command to specify it manually?
That works for me as well, as a variant to the “give up” solution.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974678586
The root problem is that `airflow dags test` is not running anything out-of-band; it triggers full-blown backfill runs, and there’s absolutely no way to distinguish those runs from backfill runs triggered by the executor. I mentioned that in #18473 and #18758; the current behaviour of this command is a big odd-ball in the big picture and does not really make sense fundamentally.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal closed issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
eladkal closed issue #19578:
URL: https://github.com/apache/airflow/issues/19578
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974678586
The root problem is that `airflow dag test` is not running anything out-of-band; it triggers full-blown backfill runs, and there’s absolutely no way to distinguish those runs from backfill runs triggered by the executor. I mentioned that in #18473 and #18758; the current behaviour of this command is a big odd-ball in the big picture and does not really make sense fundamentally.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974679199
But this case is `airflow tasks test` not the `airlfow dag tests` (and I do agree dag tests is not good).
For tasks test I thin the data interval should be inferred as in the docs, and regardles from the error reported with task tests I think `infer_data_interval` not being called at all in our code is quite a bit worrying.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974675081
Hmm @uranusjr - maybe I am missing something but I believe we simply did not plug calling `infer_data_interval` from custom timetables. I cannot find a single place where it would be called, and I believe it should be use for Custom Timetables to infer the interval for manual/test/out-of-bands runs.
I believe we simply lost it while implementation - even if it is nicely described in the docs. :)
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974683249
What still worries me - why we have the `infer_data_interval` documentaed but not used @uranusjr :) ?
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974678586
The root problem is that `airflow dags test` is not running anything out-of-band; it triggers full-blown backfill runs, and there’s absolutely no way to distinguish those runs from backfill runs triggered by the executor. I mentioned that in #18473 and #18758; the current behaviour of this command is a big odd-ball in the big picture and does not really make sense fundamentally.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974760585
Oooooh. Good catch, because the function is actually named wrong in the example! The correct function name is in fact `infer_manual_data_interval`.
https://github.com/apache/airflow/blob/9517342b727b977bcc7a99197c802bc084584c5d/airflow/timetables/base.py#L160-L167
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974674332
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974679199
But this case is `airflow tasks test` not the `airlfow dag tests` (and I do agree dag tests is not good).
For `tasks test` I think the data interval should be inferred as in the [docs](https://airflow.apache.org/docs/apache-airflow/stable/howto/timetable.html?highlight=timetables#define-scheduling-logic), and regardles from the error reported with task tests I think `infer_data_interval` not being called at all in our code is quite a bit worrying.
(But this is my first closer look at the timetable implementaion so I might have missed something)
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974684102
Because `infer_data_interval` is for inferring manual runs, and `test` commands run backfill runs! There are conceptually no way to infer a data interval for an automated (i.e. scheduled or backfill) run from a logical date, as I mentioned above.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974679199
But this case is `airflow tasks test` not the `airlfow dag tests` (and I do agree dag tests is not good).
For `tasks test` I think the data interval should be inferred as in the docs, and regardles from the error reported with task tests I think `infer_data_interval` not being called at all in our code is quite a bit worrying.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] vaci commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
vaci commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974654209
I see a similar issue when attempting to run a task using a custom Timetable, as it is then not possible to render templates in an operator.
The problem is caused by this code, which specifically checks for certain sub-classes of Timetable:
https://github.com/apache/airflow/blob/2.2.1/airflow/models/dag.py#L652
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974675081
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974684561
Yeah. yeah I understand that - but it doesn't seem to be used in the code AT ALL (or maybe I missed it when searching). I just could not find a single call to the `infer_data_interval` in the whole Airflow codebase. As far as I can see it is only mentioned in the Custom Timetable example here.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974675081
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974683249
What still worries me - why we have the `infer_data_interval` documentaed by not used @uranusjr :) ?
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974779638
Ahhh ! That explains everything :)
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-974682581
> So unless we change the semantic for `dags test` and `tasks test` (which is not trivial),
Why don't we add "data-interval' to `dags test` and `tasks tests` command to specify it manually ? Those are tests commands for user to try things out, they could add data interval there and we could provide a helpful explanation and hint what data interval they should add if they don't specify them for Custom timetable.
> The easiest solution would be to simply delete that run and re-trigger it on Airflow 2.2, or we could potentially provide a script for the user to “migrate” that existing run to 2.2.
But I think in this case the run does not even exist - so we have nothing to delete. `airflow tasks test` I believe does not even look nor modify DagRun table - as I remember (and commented in #18758) `dags tests` and `tasks tests` should not leave any traces in the DB in DagRun table (even if `dags tests` conceptually run backfill, it used DebugExecutor and - as far as I remember at least, did not rely on the DB entries). Or at least that was the intention..
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] eladkal commented on issue #19578: Custom timetable causes crash using airflow test
Posted by GitBox <gi...@apache.org>.
eladkal commented on issue #19578:
URL: https://github.com/apache/airflow/issues/19578#issuecomment-1014923279
fixed in https://github.com/apache/airflow/pull/19735
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org