[
https://issues.apache.org/jira/browse/AIRFLOW-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842205#comment-16842205
]
Jim Baldwin commented on AIRFLOW-4531:
--------------------------------------
I believe the issue may have been introduced in "[AIRFLOW-4240] State-changing
actions should be POST requests"
When this was a get the variables were passed this in the URL despite which
button was clicked &upstream=false&downstream=true&future=false&past=false
The problem seems to be in
[airflow/www/views.py|https://github.com/apache/airflow/commit/dbed51e702bf8177800183d2c4f595073aa2339d#diff-948e87b4f8f644b3ad8c7950958df033]
Now it looks like the values are being capture by objects in the form called
like:
upstream
downstream
failed_upstream
failed_downstream
success_upstream
success_downstream
But only upstream, downstream, etc is being considered in the failed and
success functions.
> Mark success and mark failed picking up clear options
> -----------------------------------------------------
>
> Key: AIRFLOW-4531
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4531
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.10.3
> Reporter: Jim Baldwin
> Assignee: Jim Baldwin
> Priority: Minor
>
> In 1.10.3 with RBAC gui. I'm noticing that in the task on click menu when I
> mark success or failure in the GUI now it will always try to mark all
> downstream tasks as no matter which options I select in the Mark Success or
> Mark Failed menus.
> 2 other users reporting the same issue in slack.
> I tested unchecking the Clear default options of downstream and recursive and
> clicking Mark Success and Mark Failed and its not attempting to clear
> downstream.
> Therefore a work around exists by setting desired options in the clear
> section.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
