lbryio/lbry-sdk

detect when server is not sending notifications

Open

#3,189 建立於 2021年2月8日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Python (7,220 star) (500 fork)batch import
area: wallethelp wanted

描述

if wallet server stops sending notifications for some reason, client should detect that and switch to another server

for example: if you send a tx and never receive a notification for it, but then you get a new block that contains an address notification for that tx, then you know the server is not sending you notifications

貢獻者指南

技術棧
python
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Pythonbasic understanding of notification systems
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the current notification mechanism in the lbry sdk, likely involving WebSocket or similar. Look at files related to wallet server communication, such as 'lbry/wallet/server.py' or 'lbry/extras/daemon.py'. The issue suggests a timeout detection: if a transaction notification is not received but later a block notification contains it, the server is faulty. A solution could involve a heartbeat or a timeout on expected notifications. Examine existing tests for notification handling to understand the flow.
detect when server is not sending notifications · lbryio/lbry-sdk#3189 | Good First Issue