Support configurable concurrent package downloads during bulk upgrades

Abierto
#6,595 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
cli, performance

Línea de trabajo

Start in the WinGet CLI upgrade path and read related issue #4105, which covers decoupling downloads from installation; compare issue #225 for the separate case of multiple connections per file. Define how a bounded queue can download packages concurrently while preserving dependency order and sequential installation, then establish completion criteria for configurable concurrency, per-package progress, and integrity checks.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Issue-Feature
Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

Please support downloading multiple package installers concurrently during winget upgrade --all, while keeping installation sequential. The current download-install-download-install flow leaves the network idle during installation.

Homebrew provides a useful example with HOMEBREW_DOWNLOAD_CONCURRENCY: https://docs.brew.sh/Manpage#environment

Proposed technical implementation details
  • Use a bounded download queue with configurable concurrency.
  • Continue downloads while one installer runs; respect dependency ordering.
  • Allow concurrency 1 for serial behavior.
  • Show per-package progress and retain integrity checks.

Related: #4105 decouples download and installation; this request adds configurable concurrent downloads across multiple packages. #225 concerns multiple connections for one file. Please consolidate under #4105 if appropriate.

Lenguaje dominante
C++
Estrellas
26.6k
Forks
1.8k
Merge medio
3 d 10 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/winget-cli

Todos los issues de microsoft/winget-cli

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.