mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-09 04:02:35 +00:00
Yichen Jiang
aa0ed35ebc
A replay must not depend on the runner's network policy, the same reason it pins its home and sessions root. The harness now honors the proxy environment, so a runner exporting one sent the web-fetch scenario's fixture request to a proxy that could not resolve the fixture host and recorded that proxy's error page. Clear the proxy names in both test-support spawners, from the one list dsh-http-proxy owns.
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.