-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[chore] Format __init__.py
files
#38044
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
BRB adding licenses. |
/format-fix pr=38044
|
But in the re-ran CI flow:
I need help. This is extremely weird — locally and in format-fix, there are no changes. But the CI flow does reformat several licences in init.py. I'd think perhaps that's because it uses I've deleted EVERYTHING from my docker and tried re-running, but I somehow nuked the whole thing and airbyte-ci just hangs without output locally, dagger container not even running. I'll try again tomorrow. 1am my time here. Three PRs stuck on this. |
Interestingly, looking at the failures, they are legit. The mentioned files don't have license header on them. Let me install the tool and run it locally without airbyte-ci to see if it helps. |
/format-fix pr=38044
|
What
Now that #38043 is up, this PR is removing flakeCheck for the Python CDK temporarily, and formats
__init__.py
files.We will add linters back when we migrate to Ruff (working on it this week). This step allows us to move forward and not have weird splitbrain formatting situation.
Also, closes https://github.com/airbytehq/airbyte-internal-issues/issues/2773!
Review
Easiest to review commit by commit — all actual formatting is in one commit, then there's another one that removes flakecheck from pyproject.toml.
Can this PR be safely reverted and rolled back?