Multi-Agent Orchestration · recorded 2026-08-29 · applies to 1 tool(s) ✓ Verified

Problem: git clone connection reset (source install path) —— Trove problem library

Verified 2026-08-29source install clone reset — clear stale git proxies and pip install deepcode-hku directly; no need to clone source.

Quick fix

# One-liner: clear the dead git proxy, then pip install directly (no source clone needed)
git config --global --unset http.proxy && git config --global --unset https.proxy && pip install deepcode-hku

What you will run into

git clone https://github.com/HKUDS/DeepCode.git keeps reporting connection reset / timeout. You think switching networks will fix it, but it still breaks after switching.

Why this happens

Two common causes:

CauseNotes
Direct GitHub from CN is unstableLarge-repo clones get reset mid-way (connectivity record)
Dead Git proxy configured locallyThe proxy is down but http.proxy remains; git going through a dead proxy always fails

One key realization: you don't need to clone at all - if you just want to use the tool, pip install directly.

git's transfer path is four stages: "proxy config -> TCP connection -> TLS handshake -> data stream".

When you see Connection reset by peer, the first three stages completed and the peer cut the connection during the data stream — the network is reachable; what broke is "transfer-channel stability", not "connectivity".

Two common root causes map to two stages: dead local proxy (git reads the http.proxy/https.proxy global config and hands traffic to a proxy that is already down;

the proxy refuses/resets) and unstable direct egress (intermediate devices reset long-lived connections on large repos).

That explains "switching networks didn't help": if the root cause is a dead proxy, changing networks changes nothing — the proxy config is still there. So the diagnostic order is fixed: git config --get http.proxy first (is there a leftover proxy?

config layer), then switch networks (physical layer), and only then blame the source.

There's also a cheaper deterministic choice: installing the tool ≠ installing the source — if you just want the tool, pip install skips the whole clone step and the problem simply doesn't exist.

Step by step

1. Clear the proxy — Required

git config --global --unset http.proxy

And git config --global --unset https.proxy; then check system proxy env vars (env | grep -i proxy).

2. Switch network / hotspot and retry — Required

Switch networks or retry off-peak; hotspot networks often bypass the egress issue.

3. Just want the tool? pip install directly — Required

pip install deepcode-hku

No source clone needed (this marketplace records the PyPI path).

How to confirm it works

Clone or pip install completes normally:

git clone ... -> completes normally (or)
pip install deepcode-hku -> Successfully installed deepcode-hku

No more Connection reset by peer.

Other environments

EnvironmentNotes
Dead proxyRestores after --unset (CSDN case)
Unstable direct connectionSwitch network/hotspot/off-peak
Just the toolpip path; skip the clone
CN connectivityDirect GitHub risks in

Symptom

git clone https://github.com/HKUDS/DeepCode.git keeps reporting connection reset / timeout.

Cause

Direct GitHub from CN is unstable; a dead Git proxy configured locally also causes resets.

Solution

  1. Clear the proxy: git config --global --unset http.proxy (and https.proxy), or check system proxy env vars.
  2. Switch network / hotspot and retry; retry off-peak.
  3. Just want the tool: pip install directly (path 1), no source clone needed.
Verification Evidence
  • Web case: CSDN (git clone connection reset -> clear Git proxy / switch hotspot, 2026-06).
  • Measured in this marketplace: recorded via the PyPI path (no clone needed); direct GitHub risks noted in the connectivity record.

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

deepcode

Source & evidence

Recorded Verified ✓ VerifiedApplies to 1 tool(s)
Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Multi-Agent Orchestration domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk