Add typing to amazon provider EMR#9969
Closed
Swalloow wants to merge 133 commits intoapache:masterfrom
Closed
Conversation
mik-laj
reviewed
Jul 24, 2020
mik-laj
reviewed
Jul 24, 2020
mik-laj
reviewed
Jul 24, 2020
mik-laj
reviewed
Jul 24, 2020
mik-laj
reviewed
Jul 24, 2020
airflow/providers/amazon/aws/operators/emr_terminate_job_flow.py
Outdated
Show resolved
Hide resolved
`action_subcommnads` -> `action_subcommands` `group_subcommnands` -> `group_subcommands`
mik-laj
reviewed
Jul 24, 2020
v2 was released on 21 March
Current available version is 1.9.0
The latest available version of jinja2 is 2.11.2 Fixes in 2.11.2: https://github.com/pallets/jinja/blob/master/CHANGES.rst#version-2112
mysqlclient was pinned as the functionality of Connection object of MySQL had changed and that it dropped python2. mysqlclient has added context manager interface to Connection which closes the connection on `__exit__` in 2.0.0 and Airflow Master no longer uses Python 2
This reverts commit c438812.
`startd_ate_lte` -> `start_date_lte`
apache#9993) Sharing session with RTIF leads to idle-in-transaction timeout error when DAG serialization is enabled and task running duration exceeds the idle-in-transaction timeout setting of the database.
Unfortunately cancelling workflows does not work from the workflows executed by forks because their tokens do not allow doing that (they are read only). So we have to run a separate cron-triggered action (in the context of apache/airflow repository to cancel all duplicate workflows. This action stops all the workflows running from the same fork/branch except the last one.
…gger_rule (apache#8867) Fixes the BaseSensorOperator to make respect the trigger_rule in downstream tasks, when setting soft_fail="True".
Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Signed-off-by: Raymond Etornam <retornam@users.noreply.github.com>
* add correct signature to operators in providers package * add keyword only to operators and sensors outside provider package * remove unused type ignore
Contributor
Author
|
@mik-laj Any updates on reviews? |
…he#10209) We are using newly added feature of GitHub to add manually triggered workflow to enable manually-triggered force-syncing of your fork with apache/airflow.
* Pylint checks should be way faster now Instead of running separate pylint checks for tests and main source we are running a single check now. This is possible thanks to a nice hack - we have pylint plugin that injects the right "# pylint: disable=" comment for all test files while reading the file content by astroid (just before tokenization) Thanks to that we can also separate out pylint checks to a separate job in CI - this way all pylint checks will be run in parallel to all other checks effectively halfing the time needed to get the static check feedback and potentially cancelling other jobs much faster. * fixup! Pylint checks should be way faster now
Replace fixed namespace "airflow" with variable {{ .Release.Namespace }}
) * Improves stability of reported coverage and makes it nicer With this change we only upload coverage report in the case when all tests were successuful and actually executed. This means that coverage report will not be run when the job gets canceled. Currently a lof of coverage reports gathered contain far less coverage because when static check fails or docs some test jobs could already submit their coverage - resulting in partial coverage reports. With this change we also remove comment from coverage report and replace it with (for now) informational status message published to github. If we see that it works, we can change it to a PR-failing status if coverage drops for a given PR. This way we might get our coverage monotonously increasing :).
While doing a trigger_dag from UI, DagRun gets created first and then WebServer starts creating TIs. Meanwhile, Scheduler also picks up the DagRun and starts creating the TIs, which results in IntegrityError as the Primary key constraint gets violated. This happens when a DAG has a good number of tasks. Also, changing the TIs array with a set for faster lookups for Dags with too many tasks.
Member
|
LGTM. Can you do a rebase? |
…into typing-aws-emr
Contributor
Author
|
@mik-laj During the rebase process, all previous history has been pushed to this PR. |
Member
|
You need to just get your commit from the top and rebase it on top of master. See the CONTRIBUTING.rst - there is a section about it in the docs and some useful links explaining what to do. |
Contributor
Author
|
Replace to #10910 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
related: #9708
Adding type annotations to
amazon/emr.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.