feat(cel-shed/p2p): bootstrapper probe tool

[smuu]

Based on @Wondertan PR: #3511

This PR introduces a new connect-bootstrappers command to the cel-shed tool. The command allows users to connect to bootstrappers of a specified network. It includes options to handle connection failures by returning errors if at least one or all bootstrappers are unreachable.

This will be used by the @celestiaorg/devops team to create alerts if no Bootstrapper is reachable.

Closes #3511

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 2.43902% with 80 lines in your changes missing coverage. Please review.

Project coverage is 46.46%. Comparing base (2469e7a) to head (ef7428c).
Report is 320 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/cel-shed/p2p.go	0.00%	78 Missing ⚠️
nodebuilder/p2p/network.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3780      +/-   ##
==========================================
+ Coverage   44.83%   46.46%   +1.62%     
==========================================
  Files         265      314      +49     
  Lines       14620    18093    +3473     
==========================================
+ Hits         6555     8407    +1852     
- Misses       7313     8669    +1356     
- Partials      752     1017     +265     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Wondertan]

Thank you for cleaning up and improving that PR!

• Linter seems to complain
• Did you test new flags work as expected?

[smuu]

Thank you for cleaning up and improving that PR!

* Linter seems to complain

* Did you test new flags work as expected?

I tried the arguments manually with these scenarios.

• All Bootstrappers are reachable
• All Bootstrappers are not reachable
• At least one Bootstrapper is reachable

Do you see a way to write tests for these?

[Wondertan]

Do you see a way to write tests for these?

We don't write tests for cel-shed usually. In some way it's bad, but on the bright side it saves a lot of time, like in this case writing a proper test is not straightforward. Usually, manual testing is enough here and that's why I am checking.

[smuu]

When running this in a container I get bash: /bin/cel-shed: cannot execute binary file: Exec format error. But I can run the celestia command in the container. cel-key fails for the same reason.

Any ideas what is going on here?

bootstrapper-probe-celestia-node-0:~$ celestia

            ____      __          __  _
          / ____/__  / /__  _____/ /_(_)___ _
         / /   / _ \/ / _ \/ ___/ __/ / __  /
        / /___/  __/ /  __(__  ) /_/ / /_/ /
        \____/\___/_/\___/____/\__/_/\__,_/

Usage:
  celestia [command]

Available Commands:
  blob        Allows to interact with the Blob Service via JSON-RPC
  bridge      Manage your Bridge node
  completion  Generate the autocompletion script for the specified shell
  das         Allows to interact with the Daser via JSON-RPC
  docgen      docgen generates the openrpc documentation for all Celestia Node packages
  full        Manage your Full node
  header      Allows interaction with the Header Module via JSON-RPC
  light       Manage your Light node
  node        Allows administrating running node.
  p2p         Allows interaction with the P2P Module via JSON-RPC
  share       Allows interaction with the Share Module via JSON-RPC
  state       Allows interaction with the State Module via JSON-RPC
  version     Show information about the current binary build

Flags:
  -h, --help   help for celestia

Additional help topics:
  celestia            

Use "celestia [command] --help" for more information about a command.
bootstrapper-probe-celestia-node-0:~$ cel-shed
bash: /bin/cel-shed: cannot execute binary file: Exec format error
bootstrapper-probe-celestia-node-0:~$ cel-key
bash: /bin/cel-key: cannot execute binary file: Exec format error

Fixed due to @tty47

[renaynay]

utack

[renaynay]

utack