You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename TaskHostResource* to TaskHostCores* for specificity
The packet pair only handles RequestCores/ReleaseCores (IBuildEngine9),
not generic 'resources'. Rename to TaskHostCoresRequest/Response to make
this explicit, matching the Stage 1 pattern (TaskHostIsRunningMultipleNodes*).
Also rename HandleResourceRequest to HandleCoresRequest in TaskHostTask.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The TaskHost node is a thin proxy for resource management. The real implicit-core/additional-core accounting happens in the in-process `TaskHost` class on the worker node:
111
111
112
112
1. Task calls `RequestCores(N)` in OutOfProcTaskHostNode
113
-
2. Sends `TaskHostResourceRequest` with `IsRelease=false` and `RequestedCores=N`
114
-
3. Worker node's `TaskHostTask.HandleResourceRequest()` calls `_buildEngine.RequestCores(N)` on the in-process TaskHost
113
+
2. Sends `TaskHostCoresRequest` with `IsRelease=false` and `RequestedCores=N`
114
+
3. Worker node's `TaskHostTask.HandleCoresRequest()` calls `_buildEngine.RequestCores(N)` on the in-process TaskHost
0 commit comments