specific method · filed under software implementation
Vendoring external dependencies
Stores copies of external dependencies in internal storage for benchmark tasks.
- source
- 1
- model
- 1
- lab adopt it
- 1
- strongest
- used
How sources treat it
One count per evidence span, weakest treatment to strongest.
used 1
Documented in
Evidence
1 span quoted from the sources, strongest treatment first.
We vendored (stored copies in internal storage) all external dependencies for tasks fix-ocaml-gc, reshard-c4-data, build-cython-ext, filter-js-from-html, sam-cell-seg, pytorch-model-cli, install-windows-3.11 and bundle the version of uv/ uvx required by all images.
usedevaluation onlyin Terminal-Bench 2.0Poolside
Filed alongside
Other methods under software implementation :: infrastructure service.
Automatic provider failoverCustom placement engineDeepSeek Elastic Compute (DSec)Dependency unificationDurable peer mailboxEnd-to-end lineageFresh-clone repository sanitizationHTTP/HTTPS sidecar proxyIn-house batch schedulerIncremental sandbox checkpointing and resumptionLocal container-image cachingModel FactoryMooncakeNeMo GuardrailsNeMo SwitchyardPer-node pooling of initialization actorsRayReplacing short-lived Ray actors with tasksSandbox pause and resumeWrite-ahead logZ3 SMT solver integration