[jira] [Commented] (AIRFLOW-6994) SparkSubmitOperator re launches spark driver even when original driver still running

[ https://issues.apache.org/jira/browse/AIRFLOW-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092042#comment-17092042 ] ASF GitHub Bot commented on AIRFLOW-6994: - stale[bot] commented on pull request #7637: URL:

[GitHub] [airflow] stale[bot] commented on pull request #7637: [AIRFLOW-6994] SparkSubmitOperator re-launches spark driver even when original driver still running

stale[bot] commented on pull request #7637: URL: https://github.com/apache/airflow/pull/7637#issuecomment-619322659 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[GitHub] [airflow] mik-laj commented on a change in pull request #8539: JIRA and Github issues explanation

mik-laj commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414965028 ## File path: CONTRIBUTING.rst ## @@ -899,6 +899,13 @@ You can join the channels via links at the `Airflow Community page

[GitHub] [airflow] mik-laj commented on a change in pull request #8481: Add hook and operator for google cloud life sciences

mik-laj commented on a change in pull request #8481: URL: https://github.com/apache/airflow/pull/8481#discussion_r414964222 ## File path: airflow/providers/google/cloud/example_dags/example_life_sciences.py ## @@ -0,0 +1,108 @@ +# +# Licensed to the Apache Software Foundation

[GitHub] [airflow] mik-laj commented on pull request #8481: Add hook and operator for google cloud life sciences

mik-laj commented on pull request #8481: URL: https://github.com/apache/airflow/pull/8481#issuecomment-619311338 The system tests only work if you have run breeze with a MySQL or Postgres database. ``` ./breeze --backend postgres ./breeze --backend mysql ``` To run

[GitHub] [airflow] mik-laj opened a new pull request #8553: Add DataflowStartSQLQuery operator

mik-laj opened a new pull request #8553: URL: https://github.com/apache/airflow/pull/8553 --- Make sure to mark the boxes below before creating PR: [x] - [X] Description above provides context of the change - [X] Unit tests coverage for changes (not needed for documentation

[GitHub] [airflow] mik-laj commented on pull request #8552: fix help message display for dags test subcommand

mik-laj commented on pull request #8552: URL: https://github.com/apache/airflow/pull/8552#issuecomment-619299600 Can you add test to avoid regression? I think something similar to the one below is enough. ``` tests/cli/test_cli_parser.py ``` ```python def

[GitHub] [airflow] houqp opened a new pull request #8552: fix help message display for dags test subcommand

houqp opened a new pull request #8552: URL: https://github.com/apache/airflow/pull/8552 Without this fix, `airflow dags test` crashes with the following error: ``` item_help = join([func(*args) for func, args in self.items]) File

[GitHub] [airflow] houqp commented on issue #8523: Json Parse Error in Tree View

houqp commented on issue #8523: URL: https://github.com/apache/airflow/issues/8523#issuecomment-619290393 turns out escape sequence itself is not escaped, @qzheng1989 feel free to test out my fix in #8551. This is an

[GitHub] [airflow] houqp opened a new pull request #8551: Fix json string escape in tree view

houqp opened a new pull request #8551: URL: https://github.com/apache/airflow/pull/8551 close #8523. --- Make sure to mark the boxes below before creating PR: [x] - [x] Description above provides context of the change - [x] Unit tests coverage for changes (not needed for

[GitHub] [airflow] potiuk commented on pull request #8549: The CRON job now is working and triggers builds on DockerHub

potiuk commented on pull request #8549: URL: https://github.com/apache/airflow/pull/8549#issuecomment-619288916 All green! This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [airflow] mik-laj opened a new pull request #8550: Add DataflowStartFlexTemplateOperator

mik-laj opened a new pull request #8550: URL: https://github.com/apache/airflow/pull/8550 --- Make sure to mark the boxes below before creating PR: [x] - [X] Description above provides context of the change - [X] Unit tests coverage for changes (not needed for documentation

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091966#comment-17091966 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[GitHub] [airflow] potiuk edited a comment on issue #8548: Add Docker compose example

potiuk edited a comment on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619235570 That would be great if you contribute. I will take a look at a few of the sources we have and try to split the changes needed into github issues over the weekend and will

[GitHub] [airflow] potiuk commented on issue #8548: Add Docker compose example

potiuk commented on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619235570 That would be great if you contribute. I will take a look at a few of the sources we have and try to split the changes needed into github issues and will welcome some contributions

[GitHub] [airflow] potiuk commented on issue #8005: Use annotated tags for releases?

potiuk commented on issue #8005: URL: https://github.com/apache/airflow/issues/8005#issuecomment-619234922 Now - we will make a nightly tag with #8549 - so the "release" tags in the future can be annotated I think - still to make a distinction. I don't think there's any harm in it. I'ts

[GitHub] [airflow] resdevd commented on issue #8548: Add Docker compose example

resdevd commented on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619234765 @potiuk Ofcourse, I've created that repo mainly for my personal preference and usecase. Feel free to use the above docker-compose code and modify if necessary. Alternatively

[GitHub] [airflow] potiuk edited a comment on issue #8460: Add ability to run some tasks on LocalExecutor but rest on Celery/DaskExecutor

potiuk edited a comment on issue #8460: URL: https://github.com/apache/airflow/issues/8460#issuecomment-619232568 I once added a POC for multiple executors based on queue - would you find it useful ?

[GitHub] [airflow] potiuk edited a comment on issue #8460: Add ability to run some tasks on LocalExecutor but rest on Celery/DaskExecutor

potiuk edited a comment on issue #8460: URL: https://github.com/apache/airflow/issues/8460#issuecomment-619232568 I once added a POC for multiple executors based on queue - would you find it useful ?https://github.com/PolideaInternal/airflow/commit/6590f665d4d9aa2629052c1af2e6f4c36a9a4dd3

[GitHub] [airflow] potiuk commented on issue #8460: Add ability to run some tasks on LocalExecutor but rest on Celery/DaskExecutor

potiuk commented on issue #8460: URL: https://github.com/apache/airflow/issues/8460#issuecomment-619232568 I once added a PR for multiple executors based on queue - would you find it useful ?https://github.com/PolideaInternal/airflow/commit/6590f665d4d9aa2629052c1af2e6f4c36a9a4dd3

[GitHub] [airflow] potiuk commented on issue #8548: Add Docker compose example

potiuk commented on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619230139 I think w would like all this to be eventually part of the Airflow repo. Ther is no point in having separate repos if this all can be added to the official airflow one. It should be

[GitHub] [airflow] potiuk opened a new pull request #8549: The CRON job now is working and triggers builds on DockerHub

potiuk opened a new pull request #8549: URL: https://github.com/apache/airflow/pull/8549 The CRON job from previous runs did not have everything working after the emergency migration to Github Actions. This change brings back following improvements: * rebuilding images from

[GitHub] [airflow] resdevd commented on issue #8548: Add Docker compose example

resdevd commented on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619205953 I’ve created a repo with Docker Compose boilerplate with official Airflow Docker images. https://github.com/resdevd/docker-compose-airflow

[GitHub] [airflow] potiuk edited a comment on pull request #8509: [AIRFLOW-4568]The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a di

potiuk edited a comment on pull request #8509: URL: https://github.com/apache/airflow/pull/8509#issuecomment-619192000 > Thank you @potiuk. However it failed again while pushing Prod image and CI image. ah.. those should be skipped in PR from.fork ... Will.look at it tomorrow

[jira] [Commented] (AIRFLOW-4568) The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowed state, such as f.i. failed

[ https://issues.apache.org/jira/browse/AIRFLOW-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091834#comment-17091834 ] ASF GitHub Bot commented on AIRFLOW-4568: - potiuk commented on pull request #8509: URL:

[jira] [Commented] (AIRFLOW-4568) The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowed state, such as f.i. failed

[ https://issues.apache.org/jira/browse/AIRFLOW-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091836#comment-17091836 ] ASF GitHub Bot commented on AIRFLOW-4568: - potiuk edited a comment on pull request #8509: URL:

[GitHub] [airflow] potiuk commented on pull request #8509: [AIRFLOW-4568]The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowe

potiuk commented on pull request #8509: URL: https://github.com/apache/airflow/pull/8509#issuecomment-619192000 > Thank you @potiuk. However it failed again while pushing Prod image and CI image. ah.. those should be skipped in PR from.foek ... Will.look at it tomorrow

[GitHub] [airflow] yordis opened a new issue #8548: Add Docker compose example

yordis opened a new issue #8548: URL: https://github.com/apache/airflow/issues/8548 Would be amazing to add some example on how to set up Airflow with the new image using Docker Compose. Example: - https://github.com/bitnami/bitnami-docker-airflow

[GitHub] [airflow] boring-cyborg[bot] commented on issue #8548: Add Docker compose example

boring-cyborg[bot] commented on issue #8548: URL: https://github.com/apache/airflow/issues/8548#issuecomment-619180374 Thanks for opening your first issue here! Be sure to follow the issue template! This is an automated

[GitHub] [airflow] boring-cyborg[bot] commented on issue #8547: Not able to trigger the DAG using api in 1.10.10

boring-cyborg[bot] commented on issue #8547: URL: https://github.com/apache/airflow/issues/8547#issuecomment-619170641 Thanks for opening your first issue here! Be sure to follow the issue template! This is an automated

[GitHub] [airflow] mnishesh opened a new issue #8547: Not able to trigger the DAG using api in 1.10.10

mnishesh opened a new issue #8547: URL: https://github.com/apache/airflow/issues/8547 Actual : even though the response status is 200 we are not able to trigger the DAG using POST API. same code is working fine in 1.10.9 expected :- API should be able to trigger the DAGS. code

[jira] [Commented] (AIRFLOW-5500) Bug in trigger api endpoint

[ https://issues.apache.org/jira/browse/AIRFLOW-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091810#comment-17091810 ] ASF GitHub Bot commented on AIRFLOW-5500: - samdjstephens commented on pull request #8081: URL:

[GitHub] [airflow] samdjstephens commented on pull request #8081: [AIRFLOW-5500] Fix the trigger_dag api in the case of nested subdags

samdjstephens commented on pull request #8081: URL: https://github.com/apache/airflow/pull/8081#issuecomment-619169385 I've run into this issue too.. Looking at places `DAG.subdags` is called: - set_is_paused - DagBag Clearly DAG.subdags was intended to return all subdags and

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091808#comment-17091808 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov opened a new pull request #8546: URL:

[GitHub] [airflow] mppetkov opened a new pull request #8546: AIRFLOW-6062 Watch worker pods from all namespaces

mppetkov opened a new pull request #8546: URL: https://github.com/apache/airflow/pull/8546 --- Make sure to mark the boxes below before creating PR: [x] - [ ] Description above provides context of the change - [ ] Unit tests coverage for changes (not needed for documentation

[GitHub] [airflow] tedmiston commented on issue #8447: Command descriptions too long

tedmiston commented on issue #8447: URL: https://github.com/apache/airflow/issues/8447#issuecomment-619164040 I am working on an initial PR for this one. This is an automated message from the Apache Git Service. To respond

[GitHub] [airflow] mik-laj edited a comment on issue #8527: Relative paths get wrong expansion

mik-laj edited a comment on issue #8527: URL: https://github.com/apache/airflow/issues/8527#issuecomment-618398091 This is behavior, which is rather difficult to change in Airflow1.10. I always recommend using paths relative to the current file. Then you can move all the file to a

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091790#comment-17091790 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091788#comment-17091788 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[GitHub] [airflow] mik-laj edited a comment on issue #8527: Relative paths get wrong expansion

mik-laj edited a comment on issue #8527: URL: https://github.com/apache/airflow/issues/8527#issuecomment-618398091 This is behavior, which is rather difficult to change in Airflow1.10. I always recommend using paths relative to the current file. Then you can move all the file to a

[GitHub] [airflow] boring-cyborg[bot] commented on pull request #8545: Xzhang/airflow sla refactoring

boring-cyborg[bot] commented on pull request #8545: URL: https://github.com/apache/airflow/pull/8545#issuecomment-619155687 Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our

[GitHub] [airflow] seanxwzhang opened a new pull request #8545: Xzhang/airflow sla refactoring

seanxwzhang opened a new pull request #8545: URL: https://github.com/apache/airflow/pull/8545 --- Make sure to mark the boxes below before creating PR: [x] - [ ] Description above provides context of the change - [ ] Unit tests coverage for changes (not needed for documentation

[GitHub] [airflow] dimberman opened a new issue #8544: Create EKS operators

dimberman opened a new issue #8544: URL: https://github.com/apache/airflow/issues/8544 **Description** The same way that we have `GKEStartPodOperator` and `GKECreateClusterOperator` we should add operators that interact with EKS and abstracts all amazon logic from the airflow user.

[GitHub] [airflow] kaxil commented on issue #8059: [AIP-31] Enable arbitrary XCom class

kaxil commented on issue #8059: URL: https://github.com/apache/airflow/issues/8059#issuecomment-619154951 +1 to Making Xcom backend pluggable with the default of `airflow.models.xcom.XCom` This is an automated message from

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091787#comment-17091787 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[GitHub] [airflow] mik-laj commented on issue #8542: Production Docker Image - quick start

mik-laj commented on issue #8542: URL: https://github.com/apache/airflow/issues/8542#issuecomment-619153953 @potiuk I think that now it should be a separate subpage. We have a guide for PIP, which contains these tables, but if Docker will use it, you can move these tables to a separate

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091771#comment-17091771 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091769#comment-17091769 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespaces are moved to status

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091768#comment-17091768 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov edited a comment on pull request #7123:

[GitHub] [airflow] mppetkov edited a comment on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov edited a comment on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 This is an automated message from the Apache Git Service. To respond to the message, please log on to

[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

[ https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091767#comment-17091767 ] ASF GitHub Bot commented on AIRFLOW-6062: - mppetkov commented on pull request #7123: URL:

[GitHub] [airflow] mppetkov commented on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace

mppetkov commented on pull request #7123: URL: https://github.com/apache/airflow/pull/7123#issuecomment-619146491 Hello, I have migrated to Airflow 1.10.10 and I am trying to use this great feature, but unfortunately when all pods from different namespace are moved to status completed,

[GitHub] [airflow] potiuk commented on issue #8439: Clean up the test_variable_commnand.py file.

potiuk commented on issue #8439: URL: https://github.com/apache/airflow/issues/8439#issuecomment-619143225 Only committers can add reviewers This is an automated message from the Apache Git Service. To respond to the

[GitHub] [airflow] houqp commented on issue #8523: Json Parse Error in Tree View

houqp commented on issue #8523: URL: https://github.com/apache/airflow/issues/8523#issuecomment-619132378 Thanks @kaxil for the tag, I will look into this. It should escape all json strings. This is an automated message

[GitHub] [airflow] potiuk commented on issue #8543: Is 1.10.10 version still saving the variable to the table? or is it only available as environment variable?

potiuk commented on issue #8543: URL: https://github.com/apache/airflow/issues/8543#issuecomment-619124620 > **Do not use issues for support requests or general help queries** > > Please ask on one of our mailing lists, or in our Slack channel. See the "Ask a question" section of

[GitHub] [airflow] boring-cyborg[bot] commented on issue #8543: Is 1.10.10 version still saving the variable to the table? or is it only available as environment variable?

boring-cyborg[bot] commented on issue #8543: URL: https://github.com/apache/airflow/issues/8543#issuecomment-619123404 Thanks for opening your first issue here! Be sure to follow the issue template! This is an automated

[GitHub] [airflow] atejano opened a new issue #8543: Is 1.10.10 version still saving the variable to the table? or is it only available as environment variable?

atejano opened a new issue #8543: URL: https://github.com/apache/airflow/issues/8543 **Do not use issues for support requests or general help queries** Please ask on one of our mailing lists, or in our Slack channel. See the "Ask a question" section of

[GitHub] [airflow] potiuk edited a comment on issue #8542: Production Docker Image - quick start

potiuk edited a comment on issue #8542: URL: https://github.com/apache/airflow/issues/8542#issuecomment-619120337 Yep. this is planned. I am gathering feedback from users in https://apache-airflow.slack.com/archives/CQAMHKWSJ and hopefully we will get useful feedback and PRs from those

[GitHub] [airflow] potiuk commented on issue #8542: Production Docker Image - quick start

potiuk commented on issue #8542: URL: https://github.com/apache/airflow/issues/8542#issuecomment-619120337 Yep. this is planned. I am gathering feedback from users in https://apache-airflow.slack.com/archives/CQAMHKWSJ and hopefully we will get useful feedback and PRs from those

[GitHub] [airflow] mik-laj opened a new issue #8542: Production Docker Image - quick start

mik-laj opened a new issue #8542: URL: https://github.com/apache/airflow/issues/8542 **Description** Hello We miss the quick start guide that will allow you to quickly launch Airflow from the official image. For now, we only have a guide that describes how to install

[GitHub] [airflow] potiuk commented on a change in pull request #8539: JIRA and Github issues explanation

potiuk commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414706765 ## File path: CONTRIBUTING.rst ## @@ -899,6 +899,13 @@ You can join the channels via links at the `Airflow Community page

[GitHub] [airflow] dinigo commented on issue #8527: Relative paths get wrong expansion

dinigo commented on issue #8527: URL: https://github.com/apache/airflow/issues/8527#issuecomment-619101078 thanks @mik-laj ! great solution. Sorry for generating overload with this sort of thing This is an automated message

[GitHub] [airflow] mik-laj commented on a change in pull request #8539: JIRA and Github issues explanation

mik-laj commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414685366 ## File path: CONTRIBUTING.rst ## @@ -879,7 +879,7 @@ Apache Airflow is a Community within Apache Software Foundation. As the motto of the Apache

[GitHub] [airflow] mik-laj commented on a change in pull request #8539: JIRA and Github issues explanation

mik-laj commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414684688 ## File path: CONTRIBUTING.rst ## @@ -879,7 +879,7 @@ Apache Airflow is a Community within Apache Software Foundation. As the motto of the Apache

[GitHub] [airflow] mik-laj commented on a change in pull request #8539: JIRA and Github issues explanation

mik-laj commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414682556 ## File path: CONTRIBUTING.rst ## @@ -899,6 +899,13 @@ You can join the channels via links at the `Airflow Community page

[GitHub] [airflow] mik-laj commented on a change in pull request #8539: JIRA and Github issues explanation

mik-laj commented on a change in pull request #8539: URL: https://github.com/apache/airflow/pull/8539#discussion_r414680414 ## File path: CONTRIBUTING.rst ## @@ -879,7 +879,7 @@ Apache Airflow is a Community within Apache Software Foundation. As the motto of the Apache

[GitHub] [airflow] ImadYIdrissi opened a new issue #8541: "TypeError: can't pickle _thread.RLock objects" on usage of BigQueryOperator

ImadYIdrissi opened a new issue #8541: URL: https://github.com/apache/airflow/issues/8541 If you need to include code snippets or logs, please put them in fenced code blocks. If they're super-long, please use the details tag like **Apache Airflow version**:1.10.2

[GitHub] [airflow] boring-cyborg[bot] commented on issue #8541: "TypeError: can't pickle _thread.RLock objects" on usage of BigQueryOperator

boring-cyborg[bot] commented on issue #8541: URL: https://github.com/apache/airflow/issues/8541#issuecomment-619080245 Thanks for opening your first issue here! Be sure to follow the issue template! This is an automated

[GitHub] [airflow] boring-cyborg[bot] commented on issue #8540: MLFlow Operator

boring-cyborg[bot] commented on issue #8540: URL: https://github.com/apache/airflow/issues/8540#issuecomment-619070439 Thanks for opening your first issue here! Be sure to follow the issue template! This is an automated

[GitHub] [airflow] felipemoz opened a new issue #8540: MLFlow Operator

felipemoz opened a new issue #8540: URL: https://github.com/apache/airflow/issues/8540 **Description** Helping MLOps team to tigger ML jobs after Airflow steps (new operator) **Use case / motivation** You can trigger mlflow jobs like sagemaker operator

[jira] [Commented] (AIRFLOW-5033) Cannot install apache-airflow[kerberos] on Python 3

[ https://issues.apache.org/jira/browse/AIRFLOW-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091629#comment-17091629 ] ASF GitHub Bot commented on AIRFLOW-5033: - elukey edited a comment on pull request #5659: URL:

[GitHub] [airflow] elukey edited a comment on pull request #5659: [AIRFLOW-5033] Switched to snakebite-py3

elukey edited a comment on pull request #5659: URL: https://github.com/apache/airflow/pull/5659#issuecomment-619054017 > On a separate note, I sent a comment above > > > I've published sasl3 package on pypi > > https://pypi.org/project/sasl3/ > >

[jira] [Commented] (AIRFLOW-5033) Cannot install apache-airflow[kerberos] on Python 3

[ https://issues.apache.org/jira/browse/AIRFLOW-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091626#comment-17091626 ] ASF GitHub Bot commented on AIRFLOW-5033: - elukey commented on pull request #5659: URL:

[GitHub] [airflow] elukey commented on pull request #5659: [AIRFLOW-5033] Switched to snakebite-py3

elukey commented on pull request #5659: URL: https://github.com/apache/airflow/pull/5659#issuecomment-619054017 > On a separate note, I sent a comment above > > > I've published sasl3 package on pypi > > https://pypi.org/project/sasl3/ > >

[GitHub] [airflow] boring-cyborg[bot] commented on pull request #8539: JIRA and Github issues explanation

boring-cyborg[bot] commented on pull request #8539: URL: https://github.com/apache/airflow/pull/8539#issuecomment-619050466 Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our

[GitHub] [airflow] mschickensoup opened a new pull request #8539: JIRA and Github issues explanation

mschickensoup opened a new pull request #8539: URL: https://github.com/apache/airflow/pull/8539 fix https://github.com/apache/airflow/issues/8271 Make sure to mark the boxes below before creating PR: [x] - [ x] Description above provides context of the change - [ x] Unit

[GitHub] [airflow] mik-laj commented on issue #8538: Verify DAG locally fails when using DAG Variable

mik-laj commented on issue #8538: URL: https://github.com/apache/airflow/issues/8538#issuecomment-619041011 You can use fallback when retrieving variables. I am also working on a feature that allows you to store variables in a JSON file. https://github.com/apache/airflow/pull/8436

[GitHub] [airflow] kaxil commented on issue #8538: Verify DAG locally fails when using DAG Variable

kaxil commented on issue #8538: URL: https://github.com/apache/airflow/issues/8538#issuecomment-619039527 From Airflow 1.10.10 you can set Environment Variables to be used as Airflow Variables. Docs:

[GitHub] [airflow] giselamorrone edited a comment on issue #7843: Colorblind friendly UI

giselamorrone edited a comment on issue #7843: URL: https://github.com/apache/airflow/issues/7843#issuecomment-618457996 @kaxil we had the same issues, and no one in our team is colorblind. For us the problem is more with failed and skipped (red and pink, they are really similar), they

[jira] [Commented] (AIRFLOW-4568) The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowed state, such as f.i. failed

[ https://issues.apache.org/jira/browse/AIRFLOW-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091577#comment-17091577 ] ASF GitHub Bot commented on AIRFLOW-4568: - randr97 commented on a change in pull request #8509:

[jira] [Commented] (AIRFLOW-4568) The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowed state, such as f.i. failed

[ https://issues.apache.org/jira/browse/AIRFLOW-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091576#comment-17091576 ] ASF GitHub Bot commented on AIRFLOW-4568: - randr97 commented on a change in pull request #8509:

[GitHub] [airflow] randr97 commented on a change in pull request #8509: [AIRFLOW-4568]The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reache

randr97 commented on a change in pull request #8509: URL: https://github.com/apache/airflow/pull/8509#discussion_r414575632 ## File path: airflow/sensors/external_task_sensor.py ## @@ -68,23 +70,35 @@ def __init__(self, external_dag_id,

[GitHub] [airflow] randr97 commented on a change in pull request #8509: [AIRFLOW-4568]The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reache

randr97 commented on a change in pull request #8509: URL: https://github.com/apache/airflow/pull/8509#discussion_r414575632 ## File path: airflow/sensors/external_task_sensor.py ## @@ -68,23 +70,35 @@ def __init__(self, external_dag_id,

[GitHub] [airflow] aaronfowles edited a comment on pull request #8536: [Airflow-7044] - add ability to specify RSA public key in extra field of SSH connection.

aaronfowles edited a comment on pull request #8536: URL: https://github.com/apache/airflow/pull/8536#issuecomment-618980157 @RosterIn please feel free to take another look. This PR, using paramiko, supports updating more elegantly and avoids having to touch the filesystem altogether.

[GitHub] [airflow] aaronfowles commented on pull request #8536: [Airflow-7044] - add ability to specify RSA public key in extra field of SSH connection.

aaronfowles commented on pull request #8536: URL: https://github.com/apache/airflow/pull/8536#issuecomment-618980157 @RosterIn please feel free to take another look. This PR, using paramiko, supports updating more elegantly avoids having to touch the filesystem altogether.

[GitHub] [airflow] CodingJonas opened a new issue #8538: Verify DAG locally fails when using DAG Variable

CodingJonas opened a new issue #8538: URL: https://github.com/apache/airflow/issues/8538 **Apache Airflow version**:1.10.10 - **OS** (e.g. from /etc/os-release): Ubuntu 18.04 - **Kernel** (e.g. `uname -a`):Linux DELL-5540-01 4.15.0-1079-oem #89-Ubuntu SMP Fri Mar 27 05:22:11

[jira] [Commented] (AIRFLOW-4568) The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disallowed state, such as f.i. failed

[ https://issues.apache.org/jira/browse/AIRFLOW-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091474#comment-17091474 ] ASF GitHub Bot commented on AIRFLOW-4568: - lokeshlal commented on pull request #8509: URL:

[GitHub] [airflow] lokeshlal commented on pull request #8509: [AIRFLOW-4568]The ExternalTaskSensor should be configurable to raise an Airflow Exception in case the poked external task reaches a disall

lokeshlal commented on pull request #8509: URL: https://github.com/apache/airflow/pull/8509#issuecomment-618948698 Thank you @potiuk. However it failed again while pushing Prod image and CI image. This is an automated

[GitHub] [airflow] potiuk opened a new issue #8537: Building backport packages can be don inside Breeze container

potiuk opened a new issue #8537: URL: https://github.com/apache/airflow/issues/8537 **Description** Currently backport packages are built on the host, but we might easily switch to building them in the container. What woudl be needed: [ ] Change the script to run

[GitHub] [airflow] ephraimbuddy commented on pull request #8481: Add hook and operator for google cloud life sciences

ephraimbuddy commented on pull request #8481: URL: https://github.com/apache/airflow/pull/8481#issuecomment-618939275 Hi @mik-laj , I didn't run the system tests. I have not been able to set it up. However I did use example dag to test it in real scenario and it worked. Can you point me

[jira] [Commented] (AIRFLOW-7111) Expose generate_presigned_url of boto3 to S3Hook

[ https://issues.apache.org/jira/browse/AIRFLOW-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091457#comment-17091457 ] ASF subversion and git services commented on AIRFLOW-7111: -- Commit

[jira] [Commented] (AIRFLOW-7111) Expose generate_presigned_url of boto3 to S3Hook

[ https://issues.apache.org/jira/browse/AIRFLOW-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091456#comment-17091456 ] ASF GitHub Bot commented on AIRFLOW-7111: - boring-cyborg[bot] commented on pull request #8441:

[jira] [Resolved] (AIRFLOW-7111) Expose generate_presigned_url of boto3 to S3Hook

[ https://issues.apache.org/jira/browse/AIRFLOW-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaxil Naik resolved AIRFLOW-7111. - Fix Version/s: 1.10.11 2.0.0 Resolution: Fixed > Expose

[GitHub] [airflow] boring-cyborg[bot] commented on pull request #8441: [AIRFLOW-7111] Add generate_presigned_url method to S3Hook

boring-cyborg[bot] commented on pull request #8441: URL: https://github.com/apache/airflow/pull/8441#issuecomment-618936768 Awesome work, congrats on your first merged pull request! This is an automated message from the

  1   2   >