ipfs/kubo

Scale deadlines and timeouts off one variable

Open

#3,456 建立於 2016年12月1日

在 GitHub 查看
 (1 留言) (1 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
help wantedtopic/libp2p

描述

IPFS is supposed to be interplanetary, with us setting timeouts for X minutes in multiple places it will be hard to get it running for interplanetary distances.

What I suggest is package with defined interface of timeouts, like connection timeout, time to live timeout and maybe "long" timeout. That then can be just change if someone wants to run IPFS on higher latency.

貢獻者指南

技術棧
go
領域
backendperformance
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programmingUnderstanding of IPFS networking
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Search for timeout constants and deadline settings across the kubo codebase, for example in Go files that handle connections, request timeouts, and TTL. Identify all places where timeouts are hardcoded or configured. Then design a centralized timeout configuration package. The issue has not been updated since 2016, so it may require maintainer input to validate the approach.