ipfs/kubo

Scale deadlines and timeouts off one variable

Open

#3456 opened on Dec 1, 2016

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedtopic/libp2p

Description

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.

Contributor guide

Tech stack
go
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingUnderstanding of IPFS networking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.