Issues with clearing large upload file tokens

オープン
#107 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
6

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Backblaze/b2-sdk-python のほかの issue

Backblaze/b2-sdk-python の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。