libp2p / libp2p/go-libp2p

Use of ActivationThresh should be documented somewhere

Open
#713 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
6.9k
Forks
1.3k
Avg merge
13d 21h
Merged PRs (30d)
1

Description

It took me quite some time to figure out why `host.Addrs()` did not return observed addrs. I was testing out some code and I was using only two peers. It would be nice if this can be configured and documented somewhere especially for the development purpose.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate ActivationThresh and trace how it affects host.Addrs() and observed addresses, especially when testing with only two peers. Document how the threshold can be configured for development and explain the resulting behavior so users can verify the setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
documentation, networking
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.