[
https://issues.apache.org/jira/browse/AIRFLOW-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906569#comment-16906569
]
ASF GitHub Bot commented on AIRFLOW-5207:
-
marcusianlevine commented on pull request #5811: [AIRFLOW-5207] Fix Mark
Success and Failure views
URL: https://github.com/apache/airflow/pull/5811
Make sure you have checked _all_ steps below.
### Jira
- [x] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-5207
### Description
- [x] Here are some details about my PR, including screenshots of any UI
changes:
After upgrading to 1.10.4, the `Mark Success` and `Mark Failure` buttons now
lead to the following error in the UI:
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason: fixes a broken view
### Commits
- [x] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [x] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
### Code Quality
- [ ] Passes `flake8`
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
