Implement Last Serial for Python Repositories

未关闭
#351 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
api, backend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

feature request high priority

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.

主要语言
Python
星标
49
派生
88
平均合并
1 天 10 小时
30 天内合并 PR
31

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pulp/pulp_python 的其他 Issue

查看 pulp/pulp_python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。