ipfs/kubo

Print dial status messages to stderr

Open

#4355 opened on Oct 30, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/enhancementtopic/commands

Description

Currently, it can be a bit difficult to debug dial errors because:

  1. We only print the last error.
  2. We don't clearly state what addresses we're trying to dial.

Printing something like,

error: ...
error: ...
dialing [3/N]: /ip4/STUFF...

would make this significantly easier to debug.

see #3933

Contributor guide

Tech stack
go
Domain
developer experiencebackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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 programmingbasic understanding of IPFS networking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Locate the dial logic in the Go codebase, likely in a package handling libp2p dials. Add Printf statements to stderr for each dial attempt and error. Ensure compatibility with existing logging patterns. Check related issue #3933 for context.