chenhg5/cc-connect · error

binary not found in archive

Error message

binary not found in archive

What it means

A sentinel from extractFromTarGz: the release tarball was scanned end-to-end but no regular entry whose name starts with 'cc-connect' was found. The archive layout is unexpected (renamed binary, packaging change), so extraction cannot proceed.

Source

Thrown at cmd/cc-connect/update.go:354

		}
		if hdr.Typeflag != tar.TypeReg {
			continue
		}
		if strings.HasPrefix(hdr.Name, "cc-connect") {
			tmp, err := os.CreateTemp("", "cc-connect-update-*")
			if err != nil {
				return "", err
			}
			if _, err := io.Copy(tmp, tr); err != nil {
				tmp.Close()
				os.Remove(tmp.Name())
				return "", fmt.Errorf("extract: %w", err)
			}
			tmp.Close()
			return tmp.Name(), nil
		}
	}
	return "", fmt.Errorf("binary not found in archive")
}

func extractFromZip(archivePath string) (string, error) {
	r, err := zip.OpenReader(archivePath)
	if err != nil {
		return "", fmt.Errorf("zip: %w", err)
	}
	defer r.Close()

	for _, f := range r.File {
		if !strings.HasPrefix(f.Name, "cc-connect") {
			continue
		}
		rc, err := f.Open()
		if err != nil {
			return "", err
		}
		tmp, err := os.CreateTemp("", "cc-connect-update-*")

View on GitHub (pinned to 4000b2338a)

Solutions

1. Download the release archive manually and inspect its layout
2. Update cc-connect tooling to a version matching the release packaging
3. File an issue if the archive genuinely lacks the binary

When it happens

Trigger: Thrown at cmd/cc-connect/update.go:354 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chenhg5/cc-connect@4000b2338a (2026-09-06). Data as JSON: /api/errors/cbccecd9b7190af4. Report an issue: GitHub.