Own sdkharness conformance and resilience checks

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
testing-qa

调研方向

Start with the contract file .sdkharness/tests.tsv, which must list all 33 conformance and 16 resilience scenarios as repository-owned, simulator-only entries. Check that each contract imports b2sdk from the exact checkout, and that dispatch rejects non-loopback endpoints and malformed scenarios or results. Done means every scenario passes against fresh sdkharness simulators with unchanged behavior, and the focused contract tests, lint, and unit gates pass. The payload does not name the individual scenario files, so mapping them is the first real task.

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

描述

The centralized sdkharness currently contains 33 b2sdk conformance implementations and 16 resilience implementations. That makes behavioral assertions live outside the repository and allows them to drift from the SDK revision they exercise.\n\nMove those executable assertions into this repository under the existing .sdkharness contract. Keep scenario inventory, simulator lifecycle, orchestration, evidence, issue reconciliation, reporting, and notification in demand-side-ai/sdkharness.\n\nAcceptance criteria:\n- .sdkharness/tests.tsv exposes all 33 conformance and 16 resilience scenarios as simulator-only repository-owned contracts.\n- Every contract imports b2sdk from the exact checkout.\n- Dispatch rejects non-loopback endpoints, malformed scenarios, and malformed or ambiguous results.\n- Existing behavior is preserved when all scenarios run against fresh sdkharness simulators.\n- Focused contract tests, repository lint, and the relevant unit gates pass.\n\nParent roadmap: backblaze-labs/demand-side-ai#744

主要语言
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 摘要。