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.

Sign up for GitHub

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

Jump to bottom

Add breeze doctor sub-command for troubleshooting #45975

Open
1 of 2 tasks
rawwar opened this issue Jan 23, 2025 · 1 comment
Open
1 of 2 tasks

Add breeze doctor sub-command for troubleshooting #45975

rawwar opened this issue Jan 23, 2025 · 1 comment
Assignees
@kunaljubce
Labels
area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code kind:feature Feature Requests

Comments

@rawwar
Copy link
Collaborator

rawwar commented Jan 23, 2025 •
edited
Loading

Description

add doctor subcommand which will help automate troubleshooting steps - https://github.com/apache/airflow/blob/main/dev/breeze/doc/04_troubleshooting.rst

Use case/motivation

slack conv: https://apache-airflow.slack.com/archives/CQ9QHSFQX/p1737638955864009?thread_ts=1737634915.083709&cid=CQ9QHSFQX

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct
@rawwar rawwar added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels Jan 23, 2025
@rawwar rawwar changed the title support breeze doctor command for troubleshooting Add breeze doctor sub-command for troubleshooting Jan 23, 2025
@rawwar rawwar assigned rawwar and unassigned rawwar Jan 23, 2025
@dosubot dosubot bot added the area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code label Jan 23, 2025
@potiuk potiuk moved this to Backlog in CI / DEV ENV planned work Jan 23, 2025
@potiuk potiuk moved this from Backlog to Ready in CI / DEV ENV planned work Jan 23, 2025
@kunaljubce
Copy link
Contributor

@rawwar Can you assign this to me?

@RNHTTR RNHTTR removed the needs-triage label for new issues that we didn't triage yet label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kunaljubce kunaljubce

Labels
area:dev-env CI, pre-commit, pylint and other changes that do not change the behavior of the final code kind:feature Feature Requests
Projects
CI / DEV ENV planned work
Status: Ready
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rawwar @RNHTTR @kunaljubce