-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
re-introduce eager service loading #12657
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
base: master
Are you sure you want to change the base?
Conversation
Test Results - Preflight, Unit21 601 tests ±0 19 955 ✅ ±0 6m 13s ⏱️ +5s Results for commit 551b4ab. ± Comparison against base commit 893018f. This pull request removes 1 and adds 1 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Test Results - Alternative Providers597 tests 419 ✅ 14m 55s ⏱️ Results for commit 551b4ab. ♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 21m 20s ⏱️ Results for commit 551b4ab. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting how we lost a feature and no one noticed 😅
Motivation
It seems we deleted eager service loading behavior with #11202 by accident.
Now with the new runtime framework, we can simply eager load services via hooks.
I've also added a proper bootstrap test to avoid deleting the behavior again without realizing it.
I updated the eager loading logic to not eager load all services if set, as it will most likely just wait forever.
My biggest question is where this hook declaration should live?
\cc @thrau @alexrashed
Changes