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

Subscriptions don't call `onUnsubscribe` if a socket is unexpectedly closed

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
redis, swift
领域
backend, databases

调研方向

Start by reading the subscription cancellation and socket error handling paths to find where onUnsubscribe is called and how unexpected closure is handled. The issue gives no file or test names, so trace those paths from the subscription entry point; done means onUnsubscribe is called when the socket closes unexpectedly as well as on formal cancellation.

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

描述

onUnsubscribe is currently only called when a subscription is formally cancelled by the user. If a socket error closes the connection, the subscription isn't alive anymore, but because onUnsubscribe isn't triggered there's no good way of knowing that this event was omitted.

I've currently worked around it using ARC retain/release calls. On deinit of a reference type, the onUnsubscribe is implied, though I'm not even certain that this works in practice.

主要语言
Swift
星标
182
派生
29
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

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

swift-server/RediStack 的其他 Issue

查看 swift-server/RediStack 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

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