-
Notifications
You must be signed in to change notification settings - Fork 1k
chore(go.mod): bump boxo fork #4114
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
Conversation
Well, we are blocked on ipfs/boxo#842 now |
aa9b9c4
to
5c5cd23
Compare
0039f17
to
f82bf26
Compare
761f320
to
023b9b2
Compare
And ipfs/boxo#872 |
This endeavour is another confirmation on why we should move away from BS |
Issue: #4151 |
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 |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edited: unintended comment
b1d622d
143b42f
to
f5399ae
Compare
As ipfs/boxo#752 is resolved now with all the reported leaks fixed,
we can now unfork boxoWe 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