ipfs/kubo

Scale deadlines and timeouts off one variable

Open

#3,456 opened on Dec 1, 2016

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

Repository metrics

Stars
 (13,906 stars)
PR merge metrics
 (Avg merge 4d 2h) (28 merged PRs in 30d)

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

Research direction
Find all hardcoded timeout values in the codebase and design a centralized configuration structure for them.
Tech stack
go
Domain
backend
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.
Half day
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70