mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-09 04:02:35 +00:00
Yichen Jiang
b239db6aeb
The Windows coverage lane failed on four cases that assume `http_proxy` and `HTTP_PROXY` are separate variables. They are one variable there: `process.env` is case-insensitive, and the launch snapshot folds names for the same reason. A scenario built on "the user set only the lowercase name" cannot exist. Two of them assert a contract rather than a spelling, so they now hold either way: what reaches a child for a scheme the user named is the user's own value and never the derived one, and a nested install carries the active policy's value rather than the outer install's published one. Both read over the pair of names instead of one. The other two are about the case distinction itself. Neither can hold on a folded environment, so each asserts what that platform does instead of skipping: the later entry wins where a preference cannot be expressed, and a diagnostic names the spelling resolution asked for. Both were verified against the folding arm rather than reasoned about.
description, kind
| description | kind |
|---|---|
| Package map for the network group: process-wide outbound transport policy that applies to every request the harness makes. | package-group |
net/ — outbound network transport
English | 中文
Summary
The net/ group owns transport-level decisions that apply to every outbound request the harness makes, regardless of which capability makes it. Today that is one decision — whether a request goes through an HTTP proxy — and one package that owns it. The group exists because such a decision belongs to no single capability: an LLM adapter, a web-search backend, an MCP transport, and a telemetry exporter all inherit it without knowing about each other, and putting it inside any of their groups would make the other three depend backwards. These packages are not capability seams: transport policy has one implementation and one answer per process, so there is nothing to swap.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
http-proxy/ |
Resolves one outbound proxy policy and installs it as the process's global dispatcher | none — installed by the launcher |
Related documentation
- Network proxy guide — the user-facing page: what to export, and why a browser is proxied when a terminal is not.
Dev Note
Working context for maintainers — click to expand
None.