Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare string values, not if strings are the same object #14942

Merged

Conversation

jedcunningham
Copy link
Member

I found this when investigating why the delete_worker_pods_on_failure flag wasn't working. The feature has sufficient test coverage, but doesn't fail simply because the strings have the same id when running in the test suite, which is exactly what happens in practice.

flake8/pylint also don't seem to raise their respective failures unless one side it literally a literal string, even though typing is applied 🤷‍♂️.

I fixed 2 other occurrences I found while I was at it.

@boring-cyborg boring-cyborg bot added provider:cncf-kubernetes Kubernetes provider related issues area:Scheduler including HA (high availability) scheduler labels Mar 22, 2021
@kaxil kaxil added this to the Airflow 2.0.2 milestone Mar 22, 2021
@github-actions github-actions bot added the full tests needed We need to run full set of tests for this PR to merge label Mar 22, 2021
@github-actions
Copy link

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

@kaxil kaxil merged commit 6d30464 into apache:master Mar 23, 2021
@kaxil kaxil deleted the fix_k8s_worker_pod_delete_failure_flag branch March 23, 2021 00:55
kaxil pushed a commit to astronomer/airflow that referenced this pull request Mar 29, 2021
I found this when investigating why the delete_worker_pods_on_failure flag wasn't working. The feature has sufficient test coverage, but doesn't fail simply because the strings have the same id when running in the test suite, which is exactly what happens in practice.

flake8/pylint also don't seem to raise their respective failures unless one side it literally a literal string, even though typing is applied 🤷‍♂️.

I fixed 2 other occurrences I found while I was at it.

(cherry picked from commit 6d30464)
kaxil pushed a commit to astronomer/airflow that referenced this pull request Apr 1, 2021
I found this when investigating why the delete_worker_pods_on_failure flag wasn't working. The feature has sufficient test coverage, but doesn't fail simply because the strings have the same id when running in the test suite, which is exactly what happens in practice.

flake8/pylint also don't seem to raise their respective failures unless one side it literally a literal string, even though typing is applied 🤷‍♂️.

I fixed 2 other occurrences I found while I was at it.

(cherry picked from commit 6d30464)
ashb pushed a commit that referenced this pull request Apr 1, 2021
I found this when investigating why the delete_worker_pods_on_failure flag wasn't working. The feature has sufficient test coverage, but doesn't fail simply because the strings have the same id when running in the test suite, which is exactly what happens in practice.

flake8/pylint also don't seem to raise their respective failures unless one side it literally a literal string, even though typing is applied 🤷‍♂️.

I fixed 2 other occurrences I found while I was at it.

(cherry picked from commit 6d30464)
ashb pushed a commit that referenced this pull request Apr 15, 2021
I found this when investigating why the delete_worker_pods_on_failure flag wasn't working. The feature has sufficient test coverage, but doesn't fail simply because the strings have the same id when running in the test suite, which is exactly what happens in practice.

flake8/pylint also don't seem to raise their respective failures unless one side it literally a literal string, even though typing is applied 🤷‍♂️.

I fixed 2 other occurrences I found while I was at it.

(cherry picked from commit 6d30464)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:Scheduler including HA (high availability) scheduler full tests needed We need to run full set of tests for this PR to merge provider:cncf-kubernetes Kubernetes provider related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants