Skip to content

chore: update go-multiaddr to v0.15 #12912

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

Closed

Conversation

MarcoPolo
Copy link
Contributor

@MarcoPolo MarcoPolo commented Feb 21, 2025

Updates the go-multiaddr dependency and this Lotus' usage of go-multiaddr. Rationale for this breaking change can be found in the draft release notes of go-multiaddr: https://github.com/multiformats/go-multiaddr/releases/. But the tl;dr is that this breaking change gets us away from the easy-to-misuse Mutliaddr interface that has led to many nil-ptr panics.

Another important thing to note:
You'll likely need this patch libp2p/go-libp2p-kad-dht#1046 backported to whatever go-libp2p-kad-dht version you're on if you don't want to update that dependency. Currently this branch points to a commit that is Lotus's current version of kad-dht (v0.25.2) plus that patch.

Requires:

@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-v015 branch from 6988a33 to 4a74a69 Compare February 21, 2025 01:25
@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-v015 branch from 4a74a69 to fbb8617 Compare February 21, 2025 01:45
@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-v015 branch from 3b1b07a to 75adfbc Compare February 21, 2025 22:38
@BigLep BigLep mentioned this pull request Jun 11, 2025
4 tasks
@rjan90
Copy link
Contributor

rjan90 commented Jun 13, 2025

Closing this as outdated - we have bumped go-multiaddrs to v0.15 in: #13173

@rjan90 rjan90 closed this Jun 13, 2025
@github-project-automation github-project-automation bot moved this from 📌 Triage to 🎉 Done in FilOz Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🎉 Done
Development

Successfully merging this pull request may close these issues.

2 participants