Implement Last Serial for Python Repositories
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 49
- Forks
- 88
- Merge medio
- 1 d 10 h
- PR fusionados (30 d)
- 31
Descripción
Original Pulp Redmine Issue: https://pulp.plan.io/issues/7491
When syncing with PyPi a check for the field last_serial is performed to see if an update is needed. Currently this field is defaulted to 0 in the sync operation so the update is always performed, but this optimization can be added by creating a last_serial field for each Python repository. This field would be passed onto the sync operation and would update after each sync. This field is currently hard-coded to 1000000000 in the PyPi live API when Pulp distributes Python content, but this value can be switch to the repository's value after it is created.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Start with the Python repository sync operation and the PyPi live API behavior described in the issue. Trace how last_serial is currently defaulted to 0 during sync and hard-coded to 1000000000 in the live API. Done means each repository stores and passes its value through sync, updates it after syncing, and the live API uses the repository value.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- api, backend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100