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

chore: Update go-multiaddr to v0.15 #3145

Merged
merged 1 commit into from
Feb 24, 2025
Merged

Conversation

MarcoPolo
Copy link
Collaborator

@MarcoPolo MarcoPolo commented Jan 20, 2025

This kicks off the great multiaddr v0.15 rollout to our dependencies. Tracked in multiformats/go-multiaddr#267.

After this PR is approved, I'll release go-multiaddr v0.15 and start the rollout.

@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-refactor branch from 894e6dc to b434cb2 Compare January 29, 2025 20:06
@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-refactor branch from bd662af to e367bc8 Compare February 12, 2025 23:04
@MarcoPolo MarcoPolo changed the title feat: Update go-multiaddr to v0.15-pre chore: Update go-multiaddr to v0.15-pre Feb 13, 2025
@MarcoPolo MarcoPolo marked this pull request as ready for review February 13, 2025 01:25
@MarcoPolo MarcoPolo requested a review from sukunrt February 13, 2025 01:29
Copy link
Member

@sukunrt sukunrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some NITs. This is obviously very difficult to review. If there's anything specific you want me to look for I can review again.

@@ -578,11 +578,11 @@ func checkDialWorkerLoopScheduling(t *testing.T, s1, s2 *Swarm, tc schedulingTes
// failDials is used to track dials which should fail in the future
// at appropriate moment a message is sent to dialState.ch to trigger
// failure
failDials := make(map[ma.Multiaddr]dialState)
failDials := make(map[*ma.Multiaddr]dialState)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add this transform, using the pointer for map key, to release notes if not already added.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already called out

@MarcoPolo MarcoPolo mentioned this pull request Feb 14, 2025
19 tasks
@sukunrt
Copy link
Member

sukunrt commented Feb 14, 2025

As there are no changes to go-multiaddr-fmt, does it mean it's already compatible with the new go-multiaddr representation?

@MarcoPolo
Copy link
Collaborator Author

MarcoPolo commented Feb 20, 2025

As there are no changes to go-multiaddr-fmt, does it mean it's already compatible with the new go-multiaddr representation?

Correct. Already compatible see: multiformats/go-multiaddr-fmt#41

@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-refactor branch from ded10c4 to 402b274 Compare February 21, 2025 00:04
@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-refactor branch from 551c603 to 8bc76c3 Compare February 24, 2025 21:53
@MarcoPolo MarcoPolo force-pushed the marco/go-multiaddr-refactor branch from 8bc76c3 to 6bccf86 Compare February 24, 2025 21:57
@MarcoPolo MarcoPolo changed the title chore: Update go-multiaddr to v0.15-pre chore: Update go-multiaddr to v0.15 Feb 24, 2025
@MarcoPolo MarcoPolo merged commit 785181f into master Feb 24, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants