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(go.mod): bump boxo fork #4114

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

chore(go.mod): bump boxo fork #4114

wants to merge 4 commits into from

Conversation

Wondertan
Copy link
Member

@Wondertan Wondertan commented Feb 12, 2025

As ipfs/boxo#752 is resolved now with all the reported leaks fixed, we can now unfork boxo

We actually can't. We found another leak induced by high peer churn. The fork now contains a few more ugly hacky changes to minimize the impact of the leak, but doesn't completely solves it. The follow up issue is on its way

@Wondertan Wondertan self-assigned this Feb 12, 2025
@Wondertan Wondertan marked this pull request as draft February 12, 2025 19:10
@Wondertan
Copy link
Member Author

Well, we are blocked on ipfs/boxo#842 now

@Wondertan Wondertan force-pushed the bump-boxo branch 2 times, most recently from aa9b9c4 to 5c5cd23 Compare March 3, 2025 14:09
@Wondertan
Copy link
Member Author

@Wondertan Wondertan marked this pull request as ready for review March 5, 2025 12:52
@Wondertan Wondertan force-pushed the bump-boxo branch 10 times, most recently from e4cbdf2 to 761f320 Compare March 6, 2025 07:56
@Wondertan Wondertan changed the title chore(go.mod): unfork boxo chore(go.mod): bump boxo fork Mar 6, 2025
@Wondertan
Copy link
Member Author

And ipfs/boxo#872

@Wondertan
Copy link
Member Author

Wondertan commented Mar 6, 2025

This endeavour is another confirmation on why we should move away from BS

@Wondertan
Copy link
Member Author

Issue: #4151

@Wondertan Wondertan enabled auto-merge (squash) March 6, 2025 15:09
@walldiss
Copy link
Member

walldiss commented Mar 6, 2025

Would be great if you can add details on what was the issue and what is the fix to PR description, because right now is not quite clear what and why are the changes

@Wondertan
Copy link
Member Author

I added a brief explanation on the issue above with link to commit having the biggest impact. I agree it would be better to explain every single change.

Copy link
Member

@walldiss walldiss left a comment

Choose a reason for hiding this comment

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

edited: unintended comment

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.

5 participants