Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
jason810496 closed pull request #65739: Fix triggerer supervisor missing server context for secrets backend URL: https://github.com/apache/airflow/pull/65739 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
jason810496 commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4798887440 As mentioned in https://github.com/apache/airflow/pull/65739#pullrequestreview-4448711493, the https://github.com/apache/airflow/pull/64022 PR should solve the issue. I will close this PR and please feel free to reopen if still encounter the same issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
potiuk commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4798344485 @edenfunf — I've removed the `ready for maintainer review` label because the next step here is yours: this branch now has **merge conflicts with `main`**. It'll go back into the maintainer queue automatically once you rebase onto the latest `main` and push — no need to re-add the label by hand. There's no rush. Automated triage note drafted by an AI-assisted tool — may get things wrong; a real Apache Airflow maintainer takes the next look once it's green. ([why automated](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md)) --- Drafted-by: Claude Code (Opus 4.8); reviewed by @potiuk before posting -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
Radu-Codrin commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4577504603 +1 - This is a very annoying bug... I wonder why it doesn't get the required attention from the community? We've paused the rollout of Airflow 3 in our environments because of this issue and we've been waiting for a fix for many weeks now. Thank you! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
potiuk commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4500359605 The PR is out there people are pinged - so it's up to them to review it . Can't do much more -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
potiuk commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4500361379 You can ping them yourself -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
psyphonix commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4499031386 Hi @potiuk , is there any possibility this could be reviewed by any other maintainers? And if this could potentially be scoped for Milestone 3.2.2 🙏 We are really eager to upgrade from our existing Airflow 2.10.x -> Airflow 3 (latest stable), however this issue is a blocker for us, due to the lack of triggerer logs visibility for our Engineers & Support Teams, making it a challenge for us to upgrade. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
edenfunf commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4359785977 @dstandish @hussein-awala Hi, could you help take a look at this PR when you have time?Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [PR] Fix triggerer supervisor missing server context for secrets backend [airflow]
boring-cyborg[bot] commented on PR #65739: URL: https://github.com/apache/airflow/pull/65739#issuecomment-4306548885 Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our [Contributors' Guide](https://github.com/apache/airflow/blob/main/contributing-docs/README.rst) Here are some useful points: - Pay attention to the quality of your code (ruff, mypy and type annotations). Our [prek-hooks]( https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst#prerequisites-for-prek-hooks) will help you with that. - In case of a new feature add useful documentation (in docstrings or in `docs/` directory). Adding a new operator? Check this short [guide](https://github.com/apache/airflow/blob/main/airflow-core/docs/howto/custom-operator.rst) Consider adding an example DAG that shows how users should use it. - Consider using [Breeze environment](https://github.com/apache/airflow/blob/main/dev/breeze/doc/README.rst) for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations. - Be patient and persistent. It might take some time to get a review or get the final approval from Committers. - Please follow [ASF Code of Conduct](https://www.apache.org/foundation/policies/conduct) for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack. - Be sure to read the [Airflow Coding style]( https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#coding-style-and-best-practices). - Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits. Apache Airflow is a community-driven project and together we are making it better 🚀. In case of doubts contact the developers at: Mailing List: [email protected] Slack: https://s.apache.org/airflow-slack -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
