Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redundant information when execute "ipfs swarm peers -v" #6167

Open
remmerw opened this issue Apr 3, 2019 · 1 comment
Open

Redundant information when execute "ipfs swarm peers -v" #6167

remmerw opened this issue Apr 3, 2019 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature need/community-input Needs input from the wider community

Comments

@remmerw
Copy link

remmerw commented Apr 3, 2019

Version information:

Type:

  • "bug": redundant information when execute "ipfs swarm peers -v"

Description:

ipfs swarm peers -v

Output:

/ip4/xxx.xxx.xxx.xxx/tcp/4001/ipfs/QmXUiYKRL7gdX354wbtj4Bc4QcgrToXRhn6zXQbXXXXX n/a inbound
/ipfs/kad/1.0.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0
/libp2p/circuit/relay/0.1.0

Only print the "/libp2p/circuit/relay/0.1.0" once should be fine. Same issue
when executing "ipfs swarm peers -v --enc=json" (Sometimes there are mutliple stream entries empty)

@Stebalien Stebalien added kind/enhancement A net-new feature or improvement to an existing feature need/community-input Needs input from the wider community labels Apr 3, 2019
@Stebalien
Copy link
Member

This just means you have a bunch of relay streams to the same peer. Ideally, we'd expose additional information on a per-stream basis but we don't have any additional information (yet).

when executing "ipfs swarm peers -v --enc=json" (Sometimes there are mutliple stream entries empty)

That means there's a stream we're currently opening but haven't finished negotiating.


I'm not sure what the best way to proceed here is so I'm going to leave this open as a discussion. The current UX is funky.

@momack2 momack2 added this to Inbox in ipfs/go-ipfs May 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature need/community-input Needs input from the wider community
Projects
No open projects
Development

No branches or pull requests

2 participants