Issues with clearing large upload file tokens

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
cloud

调研方向

Start from clear_large_file_upload_urls, which the issue says misses upload URLs that upload threads have rented out of the pool. Check how rented URLs are tracked during the rental period, then decide how to keep them invalidated, for example with a blacklist. The issue names no test file. Done means a URL rented by a thread is also invalidated when its sister tokens are cleared. The issue is open with no comments, so expect a maintainer design decision first.

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

描述

clear_large_file_upload_urls may not clear some urls that are not in the pool right now, as they are "rented" by upload threads. Those would need to be blacklisted or kept in a structure which keeps track of them even during the rental period, or something like that.

The documentation doesn't say so, but the idea behind that feature in the first place was that a failing pod is very likely to fail any subsequent requests, so the sdk code invalidates "sister" tokens to that same pod in order to save a few failing requests and go directly to retrieval of new upload urls+tokens.

It is not a severe issue - the code that improves the behavior in a corner case may be improved and I am filing this issue to not forget about this problem, maybe solve it along with some other similar issue.

主要语言
Python
星标
214
派生
68
平均合并
51 分钟
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

Backblaze/b2-sdk-python 的其他 Issue

查看 Backblaze/b2-sdk-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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