Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

delete.if-match: broken is hinted for five servers, but nothing acts on it

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading compatibility_hints.py and the delete(if_match=...) implementation; the issue says no code outside the hints file currently reads this hint. Check how server hints are represented and how DELETE handling relates to issue #740. Done means choosing and implementing a clear response when if_match is used with a server marked broken, with coverage for that behavior.

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

描述

Disclaimer: AI-generated text below the line, generated by Claude Opus 5.5, from the prompt:

file issues for the "also found"-list. [the side findings in a handover from a calendaring-client conformance-suite session]


compatibility_hints.py marks delete.if-match as broken (a DELETE with a stale If-Match deletes the object, 204) for Zimbra, Bedework 3, Bedework 5, SOGo and posteo, but delete(if_match=...) never consults the hint. No code outside the hints file reads it. On those servers delete(if_match=True) gives no protection: a concurrent change is deleted silently, which is exactly what it was meant to prevent (see https://github.com/python-caldav/caldav/issues/740).

Options:

  • warn, or raise, when if_match is used against a server hinted broken
  • document that the caller must check the hint itself
主要语言
Python
星标
412
派生
113
平均合并
9 小时 47 分钟
30 天内合并 PR
66

环境准备

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

从这里开始

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

python-caldav/caldav 的其他 Issue

查看 python-caldav/caldav 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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