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.

Sign up for GitHub

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

Jump to bottom

[ipfs/go-bitswap] [Tracking Issue] Bitswap client rewrite #214

Closed
BigLep opened this issue Mar 20, 2023 · 1 comment
Closed

[ipfs/go-bitswap] [Tracking Issue] Bitswap client rewrite #214

BigLep opened this issue Mar 20, 2023 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@BigLep
Copy link
Contributor

BigLep commented Mar 20, 2023

There has been discussion over the last couple of years of rewriting the Bitswap client code in light of challenges maintaining it and security and operational events. I couldn't find a tracking issue for it. Please remove this if there is one. I'm using this as a placeholder so can start linking expectations and related issues to it.
@BigLep BigLep added the need/triage Needs initial labeling and prioritization label Mar 20, 2023
@BigLep BigLep mentioned this issue Mar 20, 2023
Closed
@BigLep
Copy link
Contributor Author

BigLep commented Apr 26, 2023

Here is the existing tracking issue that should be used instead: #73 . I'm closing this in favor of that issue.

@BigLep BigLep closed this as not planned Won't fix, can't repro, duplicate, stale Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BigLep