This repository was archived by the owner on Aug 6, 2026. It is now read-only.
Repository navigation
fix: move WorkerPoolContextProvider higher - #1944
Merged
Merged
Conversation
Contributor
|
Reviews (1): Last reviewed commit: "fix: move WorkerPoolContextProvider high..." | Re-trigger Greptile |
adboio
approved these changes
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
We were spawning a
WorkerPoolContextProvidertoo low in the component tree, meaning we'd spawn multiple which could cause some performance issues and high RAM usage.Changes
Create 1
WorkerPoolContextProviderinstead of severalHow did you test this?
Manually