[jira] [Updated] (AIRFLOW-5694) Check for blinker when detecting Sentry packages
[
https://issues.apache.org/jira/browse/AIRFLOW-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5694:
---
Description:
{{After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying
the `[sentry]` extra, the dependency `blinker` will cause failures of the
following form: }}
{{ ../lib/python3.7/site-packages/airflow/__init__.py:40: in }}
{{ from airflow.models import DAG}}
{{ ../lib/python3.7/site-packages/airflow/models/__init__.py:21: in }}
{{ from airflow.models.baseoperator import BaseOperator # noqa: F401}}
{{ ../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
}}
{{ from airflow.models.dag import DAG}}
{{ ../lib/python3.7/site-packages/airflow/models/dag.py:51: in }}
{{ from airflow.models.taskinstance import TaskInstance,
clear_task_instances}}
{{ ../lib/python3.7/site-packages/airflow/models/taskinstance.py:53: in
}}
{{ from airflow.sentry import Sentry}}
{{ ../lib/python3.7/site-packages/airflow/sentry.py:167: in }}
{{ Sentry = ConfiguredSentry()}}
{{ ../lib/python3.7/site-packages/airflow/sentry.py:94: in __init__}}
{{ init(integrations=integrations)}}
{{ ../lib/python3.7/site-packages/sentry_sdk/hub.py:81: in _init}}
{{ client = Client(*args, **kwargs) # type: ignore}}
{{ ../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__}}
{{ self._init_impl()}}
{{ ../lib/python3.7/site-packages/sentry_sdk/client.py:108: in _init_impl}}
{{ with_defaults=self.options["default_integrations"],}}
{{ ../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82: in
setup_integrations}}
{{ type(integration).setup_once()}}
{{ ../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57: in
setup_once}}
{{ appcontext_pushed.connect(_push_appctx)}}
{{ ../lib/python3.7/site-packages/flask/signals.py:39: in _fail}}
{{ "Signalling support is unavailable because the blinker"}}
{{ E RuntimeError: Signalling support is unavailable because the blinker
library is not installed.}}
was:
After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying the
`[sentry]` extra, the dependency `blinker` will cause failures of the following
form:
../lib/python3.7/site-packages/airflow/__init__.py:40: in
from airflow.models import DAG
../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
from airflow.models.baseoperator import BaseOperator # noqa: F401
../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
from airflow.models.dag import DAG
../lib/python3.7/site-packages/airflow/models/dag.py:51: in
from airflow.models.taskinstance import TaskInstance, clear_task_instances
../lib/python3.7/site-packages/airflow/models/taskinstance.py:53: in
from airflow.sentry import Sentry
../lib/python3.7/site-packages/airflow/sentry.py:167: in
Sentry = ConfiguredSentry()
../lib/python3.7/site-packages/airflow/sentry.py:94: in __init__
init(integrations=integrations)
../lib/python3.7/site-packages/sentry_sdk/hub.py:81: in _init
client = Client(*args, **kwargs) # type: ignore
../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__
self._init_impl()
../lib/python3.7/site-packages/sentry_sdk/client.py:108: in _init_impl
with_defaults=self.options["default_integrations"],
../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82: in
setup_integrations
type(integration).setup_once()
../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57: in
setup_once
appcontext_pushed.connect(_push_appctx)
../lib/python3.7/site-packages/flask/signals.py:39: in _fail
"Signalling support is unavailable because the blinker"
E RuntimeError: Signalling support is unavailable because the blinker library
is not installed.
> Check for blinker when detecting Sentry packages
>
>
> Key: AIRFLOW-5694
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5694
> Project: Apache Airflow
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 1.10.6
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Minor
> Fix For: 1.10.6
>
>
> {{After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying
> the `[sentry]` extra, the dependency `blinker` will cause failures of the
> following form: }}
> {{ ../lib/python3.7/site-packages/airflow/__init__.py:40: in }}
> {{ from airflow.models import DAG}}
> {{ ../lib/python3.7/site-packages/airflow/models/__init__.py:21: in }}
> {{ from airflow.models.baseoperator import BaseOperator # noqa: F401}}
> {{ ../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
> }}
> {{ from airflow.models.dag import DAG}}
> {{ ../lib/python3.7/site-packages/airflow/models/dag.py:51: in }}
> {{ from air
[jira] [Updated] (AIRFLOW-5694) Check for blinker when detecting Sentry packages
[
https://issues.apache.org/jira/browse/AIRFLOW-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5694:
---
Description:
After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying the
`[sentry]` extra, the dependency `blinker` will cause failures of the following
form:
{code:python}
../lib/python3.7/site-packages/airflow/__init__.py:40: in
from airflow.models import DAG
../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
from airflow.models.baseoperator import BaseOperator # noqa: F401
../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
from airflow.models.dag import DAG
../lib/python3.7/site-packages/airflow/models/dag.py:51: in
from airflow.models.taskinstance import TaskInstance, clear_task_instances
../lib/python3.7/site-packages/airflow/models/taskinstance.py:53: in
from airflow.sentry import Sentry
../lib/python3.7/site-packages/airflow/sentry.py:167: in
Sentry = ConfiguredSentry()
../lib/python3.7/site-packages/airflow/sentry.py:94: in __init__
init(integrations=integrations)
../lib/python3.7/site-packages/sentry_sdk/hub.py:81: in _init
client = Client(*args, **kwargs) # type: ignore
../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__
self._init_impl()
../lib/python3.7/site-packages/sentry_sdk/client.py:108: in _init_impl
with_defaults=self.options["default_integrations"],
../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82: in
setup_integrations
type(integration).setup_once()
../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57: in
setup_once
appcontext_pushed.connect(_push_appctx)
../lib/python3.7/site-packages/flask/signals.py:39: in _fail
"Signalling support is unavailable because the blinker"
E RuntimeError: Signalling support is unavailable because the blinker library
is not installed.
{code}
was:
After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying the
`[sentry]` extra, the dependency `blinker` will cause failures of the following
form:
{code:java}
../lib/python3.7/site-packages/airflow/__init__.py:40: in from
airflow.models import
DAG../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
from airflow.models.baseoperator import BaseOperator # noqa:
F401../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
from airflow.models.dag import
DAG../lib/python3.7/site-packages/airflow/models/dag.py:51: in from
airflow.models.taskinstance import TaskInstance,
clear_task_instances../lib/python3.7/site-packages/airflow/models/taskinstance.py:53:
in from airflow.sentry import
Sentry../lib/python3.7/site-packages/airflow/sentry.py:167: in
Sentry = ConfiguredSentry()../lib/python3.7/site-packages/airflow/sentry.py:94:
in __init__
init(integrations=integrations)../lib/python3.7/site-packages/sentry_sdk/hub.py:81:
in _init client = Client(*args, **kwargs) # type:
ignore../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__
self._init_impl()../lib/python3.7/site-packages/sentry_sdk/client.py:108: in
_init_impl
with_defaults=self.options["default_integrations"],../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82:
in setup_integrations
type(integration).setup_once()../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57:
in setup_once
appcontext_pushed.connect(_push_appctx)../lib/python3.7/site-packages/flask/signals.py:39:
in _fail "Signalling support is unavailable because the blinker"E
RuntimeError: Signalling support is unavailable because the blinker library is
not installed.
{code}
> Check for blinker when detecting Sentry packages
>
>
> Key: AIRFLOW-5694
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5694
> Project: Apache Airflow
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 1.10.6
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Minor
> Fix For: 1.10.6
>
>
> After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying
> the `[sentry]` extra, the dependency `blinker` will cause failures of the
> following form:
> {code:python}
> ../lib/python3.7/site-packages/airflow/__init__.py:40: in
> from airflow.models import DAG
> ../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
> from airflow.models.baseoperator import BaseOperator # noqa: F401
> ../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
> from airflow.models.dag import DAG
> ../lib/python3.7/site-packages/airflow/models/dag.py:51: in
> from airflow.models.taskinstance import TaskInstance, clear_task_instances
> ../lib/python3.7/site-packages/airflow/models/tas
[jira] [Updated] (AIRFLOW-5694) Check for blinker when detecting Sentry packages
[
https://issues.apache.org/jira/browse/AIRFLOW-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5694:
---
Description:
After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying the
`[sentry]` extra, the dependency `blinker` will cause failures of the following
form:
{code:java}
../lib/python3.7/site-packages/airflow/__init__.py:40: in from
airflow.models import
DAG../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
from airflow.models.baseoperator import BaseOperator # noqa:
F401../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
from airflow.models.dag import
DAG../lib/python3.7/site-packages/airflow/models/dag.py:51: in from
airflow.models.taskinstance import TaskInstance,
clear_task_instances../lib/python3.7/site-packages/airflow/models/taskinstance.py:53:
in from airflow.sentry import
Sentry../lib/python3.7/site-packages/airflow/sentry.py:167: in
Sentry = ConfiguredSentry()../lib/python3.7/site-packages/airflow/sentry.py:94:
in __init__
init(integrations=integrations)../lib/python3.7/site-packages/sentry_sdk/hub.py:81:
in _init client = Client(*args, **kwargs) # type:
ignore../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__
self._init_impl()../lib/python3.7/site-packages/sentry_sdk/client.py:108: in
_init_impl
with_defaults=self.options["default_integrations"],../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82:
in setup_integrations
type(integration).setup_once()../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57:
in setup_once
appcontext_pushed.connect(_push_appctx)../lib/python3.7/site-packages/flask/signals.py:39:
in _fail "Signalling support is unavailable because the blinker"E
RuntimeError: Signalling support is unavailable because the blinker library is
not installed.
{code}
was:
{{After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying
the `[sentry]` extra, the dependency `blinker` will cause failures of the
following form: }}
{{ ../lib/python3.7/site-packages/airflow/__init__.py:40: in }}
{{ from airflow.models import DAG}}
{{ ../lib/python3.7/site-packages/airflow/models/__init__.py:21: in }}
{{ from airflow.models.baseoperator import BaseOperator # noqa: F401}}
{{ ../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
}}
{{ from airflow.models.dag import DAG}}
{{ ../lib/python3.7/site-packages/airflow/models/dag.py:51: in }}
{{ from airflow.models.taskinstance import TaskInstance,
clear_task_instances}}
{{ ../lib/python3.7/site-packages/airflow/models/taskinstance.py:53: in
}}
{{ from airflow.sentry import Sentry}}
{{ ../lib/python3.7/site-packages/airflow/sentry.py:167: in }}
{{ Sentry = ConfiguredSentry()}}
{{ ../lib/python3.7/site-packages/airflow/sentry.py:94: in __init__}}
{{ init(integrations=integrations)}}
{{ ../lib/python3.7/site-packages/sentry_sdk/hub.py:81: in _init}}
{{ client = Client(*args, **kwargs) # type: ignore}}
{{ ../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__}}
{{ self._init_impl()}}
{{ ../lib/python3.7/site-packages/sentry_sdk/client.py:108: in _init_impl}}
{{ with_defaults=self.options["default_integrations"],}}
{{ ../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82: in
setup_integrations}}
{{ type(integration).setup_once()}}
{{ ../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57: in
setup_once}}
{{ appcontext_pushed.connect(_push_appctx)}}
{{ ../lib/python3.7/site-packages/flask/signals.py:39: in _fail}}
{{ "Signalling support is unavailable because the blinker"}}
{{ E RuntimeError: Signalling support is unavailable because the blinker
library is not installed.}}
> Check for blinker when detecting Sentry packages
>
>
> Key: AIRFLOW-5694
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5694
> Project: Apache Airflow
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 1.10.6
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Minor
> Fix For: 1.10.6
>
>
> After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying
> the `[sentry]` extra, the dependency `blinker` will cause failures of the
> following form:
> {code:java}
> ../lib/python3.7/site-packages/airflow/__init__.py:40: in from
> airflow.models import
> DAG../lib/python3.7/site-packages/airflow/models/__init__.py:21: in
> from airflow.models.baseoperator import BaseOperator # noqa:
> F401../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in
> from airflow.models.dag import
> DAG../lib/python3.7/site-packages/airflow/models/dag.py:51: in
> from airflow.models.
[jira] [Created] (AIRFLOW-5694) Check for blinker when detecting Sentry packages
Marcus Levine created AIRFLOW-5694: -- Summary: Check for blinker when detecting Sentry packages Key: AIRFLOW-5694 URL: https://issues.apache.org/jira/browse/AIRFLOW-5694 Project: Apache Airflow Issue Type: Bug Components: dependencies Affects Versions: 1.10.6 Reporter: Marcus Levine Assignee: Marcus Levine Fix For: 1.10.6 After upgrading to 1.10.6rc1 with `sentry-sdk` installed but not specifying the `[sentry]` extra, the dependency `blinker` will cause failures of the following form: ../lib/python3.7/site-packages/airflow/__init__.py:40: in from airflow.models import DAG ../lib/python3.7/site-packages/airflow/models/__init__.py:21: in from airflow.models.baseoperator import BaseOperator # noqa: F401 ../lib/python3.7/site-packages/airflow/models/baseoperator.py:42: in from airflow.models.dag import DAG ../lib/python3.7/site-packages/airflow/models/dag.py:51: in from airflow.models.taskinstance import TaskInstance, clear_task_instances ../lib/python3.7/site-packages/airflow/models/taskinstance.py:53: in from airflow.sentry import Sentry ../lib/python3.7/site-packages/airflow/sentry.py:167: in Sentry = ConfiguredSentry() ../lib/python3.7/site-packages/airflow/sentry.py:94: in __init__ init(integrations=integrations) ../lib/python3.7/site-packages/sentry_sdk/hub.py:81: in _init client = Client(*args, **kwargs) # type: ignore ../lib/python3.7/site-packages/sentry_sdk/client.py:80: in __init__ self._init_impl() ../lib/python3.7/site-packages/sentry_sdk/client.py:108: in _init_impl with_defaults=self.options["default_integrations"], ../lib/python3.7/site-packages/sentry_sdk/integrations/__init__.py:82: in setup_integrations type(integration).setup_once() ../lib/python3.7/site-packages/sentry_sdk/integrations/flask.py:57: in setup_once appcontext_pushed.connect(_push_appctx) ../lib/python3.7/site-packages/flask/signals.py:39: in _fail "Signalling support is unavailable because the blinker" E RuntimeError: Signalling support is unavailable because the blinker library is not installed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Levine closed AIRFLOW-4430. -- > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.4 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 1.10.4 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Levine updated AIRFLOW-4430: --- Fix Version/s: (was: 2.0.0) 1.10.4 > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.4 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 1.10.4 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919026#comment-16919026 ] Marcus Levine commented on AIRFLOW-4430: [~kaxilnaik] this bug was only ever detected in a pre-release commit of 1.10.4 - it didn't end up being an issue in the final release I think this can be marked as fixed in 1.10.4 and closed > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.4 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 2.0.0 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (AIRFLOW-5207) Mark Success and Mark Failed views error out due to DAG reassignment
[
https://issues.apache.org/jira/browse/AIRFLOW-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine closed AIRFLOW-5207.
--
Resolution: Not A Problem
This turned out to be an issue with one of our plugins
> Mark Success and Mark Failed views error out due to DAG reassignment
>
>
> Key: AIRFLOW-5207
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5207
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.4
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.5
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When trying to clear a task after upgrading to 1.10.4, I get the following
> traceback:
> {code:java}
> File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line
> 1451, in failed future, past, State.FAILED) File
> "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
> _mark_task_instance_state task.dag = dag File
> "/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
> 509, in dag "The DAG assigned to {} can not be changed.".format(self))
> airflow.exceptions.AirflowException: The DAG assigned to
> can not be changed.{code}
> This should be a simple fix by either dropping the offending line, or if it
> is required to keep things working, just set the private attribute instead:
> {code:java}
> task._dag = dag
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AIRFLOW-5207) Mark Success and Mark Failed views error out due to DAG reassignment
[
https://issues.apache.org/jira/browse/AIRFLOW-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5207:
---
Description:
When trying to clear a task after upgrading to 1.10.4, I get the following
traceback:
{code:java}
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.{code}
This should be a simple fix by either dropping the offending line, or if it is
required to keep things working, just set the private attribute instead:
{code:java}
task._dag = dag
{code}
was:
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
{code:java}
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.{code}
This should be a simple fix by either dropping the offending line, or if it is
required to keep things working, just set the private attribute instead:
{code:java}
task._dag = dag
{code}
> Mark Success and Mark Failed views error out due to DAG reassignment
>
>
> Key: AIRFLOW-5207
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5207
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.4
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.5
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When trying to clear a task after upgrading to 1.10.4, I get the following
> traceback:
> {code:java}
> File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line
> 1451, in failed future, past, State.FAILED) File
> "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
> _mark_task_instance_state task.dag = dag File
> "/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
> 509, in dag "The DAG assigned to {} can not be changed.".format(self))
> airflow.exceptions.AirflowException: The DAG assigned to
> can not be changed.{code}
> This should be a simple fix by either dropping the offending line, or if it
> is required to keep things working, just set the private attribute instead:
> {code:java}
> task._dag = dag
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AIRFLOW-5207) Mark Success and Mark Failed views error out due to DAG reassignment
[
https://issues.apache.org/jira/browse/AIRFLOW-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5207:
---
Description:
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
{code:java}
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.{code}
This should be a simple fix by either dropping the `task.dag = dag` line, or if
it is required to keep things working, just set the private attribute instead:
`task._dag = dag`
was:
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
```
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.
```
This should be a simple fix by either dropping the `task.dag = dag` line, or if
it is required to keep things working, just set the private attribute instead:
`task._dag = dag`
> Mark Success and Mark Failed views error out due to DAG reassignment
>
>
> Key: AIRFLOW-5207
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5207
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.4
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.5
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When trying to clear a task after upgrading to `1.10.4`, I get the following
> traceback:
> {code:java}
> File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line
> 1451, in failed future, past, State.FAILED) File
> "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
> _mark_task_instance_state task.dag = dag File
> "/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
> 509, in dag "The DAG assigned to {} can not be changed.".format(self))
> airflow.exceptions.AirflowException: The DAG assigned to
> can not be changed.{code}
> This should be a simple fix by either dropping the `task.dag = dag` line, or
> if it is required to keep things working, just set the private attribute
> instead: `task._dag = dag`
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AIRFLOW-5207) Mark Success and Mark Failed views error out due to DAG reassignment
[
https://issues.apache.org/jira/browse/AIRFLOW-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-5207:
---
Description:
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
{code:java}
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.{code}
This should be a simple fix by either dropping the offending line, or if it is
required to keep things working, just set the private attribute instead:
{code:java}
task._dag = dag
{code}
was:
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
{code:java}
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.{code}
This should be a simple fix by either dropping the `task.dag = dag` line, or if
it is required to keep things working, just set the private attribute instead:
`task._dag = dag`
> Mark Success and Mark Failed views error out due to DAG reassignment
>
>
> Key: AIRFLOW-5207
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5207
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.4
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.5
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When trying to clear a task after upgrading to `1.10.4`, I get the following
> traceback:
> {code:java}
> File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line
> 1451, in failed future, past, State.FAILED) File
> "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
> _mark_task_instance_state task.dag = dag File
> "/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
> 509, in dag "The DAG assigned to {} can not be changed.".format(self))
> airflow.exceptions.AirflowException: The DAG assigned to
> can not be changed.{code}
> This should be a simple fix by either dropping the offending line, or if it
> is required to keep things working, just set the private attribute instead:
> {code:java}
> task._dag = dag
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (AIRFLOW-5207) Mark Success and Mark Failed views error out due to DAG reassignment
Marcus Levine created AIRFLOW-5207:
--
Summary: Mark Success and Mark Failed views error out due to DAG
reassignment
Key: AIRFLOW-5207
URL: https://issues.apache.org/jira/browse/AIRFLOW-5207
Project: Apache Airflow
Issue Type: Bug
Components: ui
Affects Versions: 1.10.4
Reporter: Marcus Levine
Assignee: Marcus Levine
Fix For: 1.10.5
When trying to clear a task after upgrading to `1.10.4`, I get the following
traceback:
```
File "/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1451,
in failed future, past, State.FAILED) File
"/usr/local/lib/python3.7/site-packages/airflow/www/views.py", line 1396, in
_mark_task_instance_state task.dag = dag File
"/usr/local/lib/python3.7/site-packages/airflow/models/baseoperator.py", line
509, in dag "The DAG assigned to {} can not be changed.".format(self))
airflow.exceptions.AirflowException: The DAG assigned to can not be changed.
```
This should be a simple fix by either dropping the `task.dag = dag` line, or if
it is required to keep things working, just set the private attribute instead:
`task._dag = dag`
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Levine updated AIRFLOW-4430: --- Fix Version/s: (was: 2.0.0) 1.10.5 > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.4 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 1.10.5 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Levine updated AIRFLOW-4430: --- Affects Version/s: 1.10.4 > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.4 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 2.0.0 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
[ https://issues.apache.org/jira/browse/AIRFLOW-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AIRFLOW-4430 started by Marcus Levine. -- > Improper link on "Zoom into SubDAG" button > -- > > Key: AIRFLOW-4430 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 > Project: Apache Airflow > Issue Type: Bug > Components: ui >Affects Versions: 1.10.3 >Reporter: Marcus Levine >Assignee: Marcus Levine >Priority: Major > Fix For: 1.10.4 > > > The "Zoom into SubDAG" link in the task detail modal for subDAGs does not > link to the proper location, instead it points to the default DAG view for > the current, top-level DAG (not the subDAG) > > In the "example_subdag_operator" DAG for instance, the subDAG link provided > on the button for "section-1" is > "/tree?dag_id=example_subdag_operator&execution_date=..." instead of > "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRFLOW-4430) Improper link on "Zoom into SubDAG" button
Marcus Levine created AIRFLOW-4430: -- Summary: Improper link on "Zoom into SubDAG" button Key: AIRFLOW-4430 URL: https://issues.apache.org/jira/browse/AIRFLOW-4430 Project: Apache Airflow Issue Type: Bug Components: ui Affects Versions: 1.10.3 Reporter: Marcus Levine Fix For: 1.10.4 The "Zoom into SubDAG" link in the task detail modal for subDAGs does not link to the proper location, instead it points to the default DAG view for the current, top-level DAG (not the subDAG) In the "example_subdag_operator" DAG for instance, the subDAG link provided on the button for "section-1" is "/tree?dag_id=example_subdag_operator&execution_date=..." instead of "/tree?dag_id=example_subdag_operator.section-1&execution_date=..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on AIRFLOW-4300 started by Marcus Levine.
--
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.4
>
>
> After upgrading to 1.10.3, the task detail modal that normally appears when
> clicking on a task from the graph view does not appear when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by 'try_number'
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine reassigned AIRFLOW-4300:
--
Assignee: Marcus Levine
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Assignee: Marcus Levine
>Priority: Major
> Fix For: 1.10.4
>
>
> After upgrading to 1.10.3, the task detail modal that normally appears when
> clicking on a task from the graph view does not appear when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by 'try_number'
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the model window that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the task detail modal that normally appears when
clicking on a task from the graph view no longer appears when the DAG has not
been run yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the task detail modal that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the task detail modal that normally appears when
clicking on a task from the graph view does not appear when the DAG has not
been run yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by 'try_number'
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the task detail modal that normally appears when
clicking on a task from the graph view no longer appears when the DAG has not
been run yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by 'try_number'
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the task detail modal that normally appears when
> clicking on a task from the graph view does not appear when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by 'try_number'
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the task detail modal that normally appears when
clicking on a task from the graph view no longer appears when the DAG has not
been run yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by 'try_number'
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the task detail modal that normally appears when
clicking on a task from the graph view no longer appears when the DAG has not
been run yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue is caused by `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the task detail modal that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue is caused by 'try_number'
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template before
prior to running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the model window that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template before
> prior to running the DAG
> In the JavaScript console, it appears this issue emerges from `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template prior to
running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template before
prior to running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the model window that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template prior
> to running the DAG
> In the JavaScript console, it appears this issue emerges from `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the model window that normally appears when clicking
on a task from the graph view no longer appears when the DAG has not been run
yet
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that pops up when clicking on a
task in a DAG that has not been run yet no longer appears
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the model window that normally appears when
> clicking on a task from the graph view no longer appears when the DAG has not
> been run yet
> This makes it impossible to see the task details and rendered template before
> actually running the DAG
> In the JavaScript console, it appears this issue emerges from `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
Marcus Levine created AIRFLOW-4300:
--
Summary: Task Modal Broken for DAGs that have not run
Key: AIRFLOW-4300
URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
Project: Apache Airflow
Issue Type: Bug
Components: ui
Affects Versions: 1.10.3
Reporter: Marcus Levine
After upgrading to 1.10.3, the model window that pops up when clicking on a
task in a DAG that has not been run yet no longer appears
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRFLOW-4300) Task Modal Broken for DAGs that have not run
[
https://issues.apache.org/jira/browse/AIRFLOW-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Levine updated AIRFLOW-4300:
---
Description:
After upgrading to 1.10.3, the model window that pops up when clicking on a
task in a DAG that has not been run yet no longer appears
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
was:
After upgrading to 1.10.3, the model window that pops up when clicking on a
task in a DAG that has not been run yet no longer appears
This makes it impossible to see the task details and rendered template before
actually running the DAG
In the JavaScript console, it appears this issue emerges from `try_number`
being undefined when the DAG has not been run yet:
{code:java}
Uncaught TypeError: Cannot read property 'try_number' of undefined
at SVGGElement. (graph?dag_id=my-dag:1)
at SVGGElement.__onclick (d3.v3.min.js:1)
{code}
> Task Modal Broken for DAGs that have not run
>
>
> Key: AIRFLOW-4300
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4300
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
>Affects Versions: 1.10.3
>Reporter: Marcus Levine
>Priority: Major
>
> After upgrading to 1.10.3, the model window that pops up when clicking on a
> task in a DAG that has not been run yet no longer appears
> This makes it impossible to see the task details and rendered template before
> actually running the DAG
> In the JavaScript console, it appears this issue emerges from `try_number`
> being undefined when the DAG has not been run yet:
> {code:java}
> Uncaught TypeError: Cannot read property 'try_number' of undefined
> at SVGGElement. (graph?dag_id=my-dag:1)
> at SVGGElement.__onclick (d3.v3.min.js:1)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
