Skip to content

Make it possible to opt in to TaskScheduler auto-configuration when a TaskScheduler or ScheduledExecutorService has already been defined #44806

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

Closed
wilkinsona opened this issue Mar 20, 2025 · 1 comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement

Comments

@wilkinsona
Copy link
Member

This is the task scheduling equivalent of #44659.

@snicoll
Copy link
Member

snicoll commented Mar 26, 2025

Now that #44659 is implemented, we don't think parity is required here as the conditions that make the scheduling auto-configuration to back off are much more narrowed. We can reconsider if someone has a compelling use case.

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Mar 26, 2025
@snicoll snicoll added status: declined A suggestion or change that we don't feel we should currently apply and removed status: pending-design-work Needs design work before any code can be developed labels Mar 26, 2025
@wilkinsona wilkinsona removed this from the 3.5.x milestone Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants