Conversation
|
|
|
Given that we now use the workspace root, for most users what should happen is that servers started on the same monorepo will all share the same root, so The PR also supports starting a server in a root that is a child of active config roots (in that case it is a matter of expanding one of the parent roots until it). This only happens if an active root was a parent out of the monorepo. If it isn't a child of any active config root, then we create a new direntCache (and expand it to connect it to any active config root that is a child of it). |
|
/ecosystem-ci run |
This comment was marked as outdated.
This comment was marked as outdated.
|
/ecosystem-ci run |
This comment was marked as outdated.
This comment was marked as outdated.
|
/ecosystem-ci run |
This comment was marked as outdated.
This comment was marked as outdated.
|
/ecosystem-ci run |
This comment was marked as outdated.
This comment was marked as outdated.
|
/ecosystem-ci run |
|
📝 Ran ecosystem CI on
|
|
astro, marko, and vitepress are failing with this PR. Even with its simplest form of only sharing the cache if the root is exactly the same for a config (that it would still be good given that we now use the workspace root for each config). |
Description
Follow up to:
Implements an idea we discussed with @sheremet-va, sharing the DirentCache trees between FsUtils of different servers. In Vitest workspace mode this should avoid duplicating the trees of overlapping roots.
Pushing it as a draft for now. We should first merge #15279.
What is the purpose of this pull request?