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

D205 Support - Stragglers #33301

Merged
merged 3 commits into from
Aug 15, 2023

Conversation

ferruzzi
Copy link
Contributor

Part of #10742

D205 asserts that all docstrings must have a one-line summary ending in a period. If there is more than one sentence then there must be a blank line before the rest of the docstring. Meeting these requirements could be as simple as adding a newline, or might require some rephrasing.

There are almost a thousand violations in the repo so we're going to have to take this in bites.

PLEASE NOTE

There should be zero logic changes in this PR, only changes to docstrings and whitespace. If you see otherwise, please call it out.

Included in this chunk

A handful of files which weren't in clusters big enough to warrant their own PRs.

To test

If you comment out this line and run pre-commit in main you will get 92 errors. After these changes, only 76 remain and no files in the list above should be on the list. After uncommenting that line and rerunning pre-commits, there should be zero regressions.

@ferruzzi
Copy link
Contributor Author

error An unexpected error occurred: "https://registry.yarnpkg.com/@webassemblyjs/helper-wasm-bytecode/-/helper-wasm-bytecode-1.11.1.tgz: Request failed \"500 Internal Server Error\"".

@@ -181,7 +181,10 @@ def _push_tasks(cls, operator: AbstractOperator | list[AbstractOperator], setup:

@classmethod
def _update_teardown_downstream(cls, operator: AbstractOperator | list[AbstractOperator]):
"""This recursively goes through the tasks downstream of the setup in the context manager,
"""
Update _teardown_downstream_of_setup.
Copy link
Member

@uranusjr uranusjr Aug 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dstandish Any idea to better describe this function? (Also _update_setup_upstream below)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I've found suitable phrasing here and for the other method below.

# Conflicts:
#	airflow/triggers/external_task.py
#	airflow/utils/setup_teardown.py
@uranusjr uranusjr merged commit 9bf68ad into apache:main Aug 15, 2023
48 checks passed
ferruzzi added a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Aug 17, 2023
@ephraimbuddy ephraimbuddy added this to the Airflow 2.7.1 milestone Aug 27, 2023
@ephraimbuddy ephraimbuddy added the type:misc/internal Changelog: Misc changes that should appear in change log label Aug 27, 2023
ephraimbuddy pushed a commit that referenced this pull request Aug 28, 2023
(cherry picked from commit 9bf68ad)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core-operators Operators, Sensors and hooks within Core Airflow area:plugins area:providers area:Triggerer provider:papermill type:misc/internal Changelog: Misc changes that should appear in change log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants