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: bump libp2p to v0.33.2 #4655

Merged
merged 2 commits into from
Apr 23, 2024
Merged

chore: bump libp2p to v0.33.2 #4655

merged 2 commits into from
Apr 23, 2024

Conversation

acha-bill
Copy link
Contributor

No description provided.

@acha-bill acha-bill requested a review from istae April 23, 2024 09:51
@acha-bill acha-bill assigned janos and unassigned janos Apr 23, 2024
@acha-bill acha-bill requested a review from janos April 23, 2024 09:57
@istae istae merged commit a9215e0 into master Apr 23, 2024
14 checks passed
@istae istae deleted the libp2p-v0.33.2 branch April 23, 2024 11:10
Copy link
Member

@janos janos left a comment

Choose a reason for hiding this comment

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

The upgrade is ok from the libp2p package api, but it should be tested against nodes that run libp2p v0.30.0 for possible regressions. I suggest to have some canary nodes updates that currently have memory issues visible on the metrics dashboards.

The upgrade for the whole libp2p stack is quite extensive in order to fix a timer leak with a one line. If problems are detected, I suggest to use a patched version of libp2p v0.30.0 and to deal with the complexities of extensive testing in time, without rush, as this memory leak is an urgent issue.

istae pushed a commit that referenced this pull request Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants