-
Notifications
You must be signed in to change notification settings - Fork 48
Issues: ipfs/js-ipfs-bitswap
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Implement bitswap sessions
exp/expert
Having worked on the specific codebase is important
kind/enhancement
A net-new feature or improvement to an existing feature
#625
opened Jan 9, 2024 by
achingbrain
SortedMap signature mismatch from Map
need/triage
Needs initial labeling and prioritization
#617
opened Dec 27, 2023 by
linuxninja39
feat: stop automatically verifying bytes
need/triage
Needs initial labeling and prioritization
#603
opened Oct 10, 2023 by
SgtPooki
bug: fs.cat hanging
effort/days
Estimated to take multiple days, but less than a week
exp/intermediate
Prior experience is likely helpful
status/ready
Ready to be worked
#604
opened Sep 28, 2023 by
SgtPooki
feat: return providing peer(s) in Estimated to take one or several hours
exp/beginner
Can be confidently tackled by newcomers
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
P2
Medium: Good to have, but can wait until someone steps up
status/ready
Ready to be worked
bitswap:want-block:block
event
effort/hours
#586
opened Jul 27, 2023 by
SgtPooki
Remove incoming stream timeout?
need/triage
Needs initial labeling and prioritization
#523
opened Feb 8, 2023 by
achingbrain
v12 not working - opens connection but then no data is received
need/triage
Needs initial labeling and prioritization
#456
opened Jul 6, 2022 by
alanshaw
Bitswap Improvements Landed in js-ipfs?
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
P3
Low: Not priority right now
#424
opened Dec 26, 2021 by
christroutner
Fix inconsistencies discovered in #261
status/ready
Ready to be worked
#303
opened Mar 10, 2021 by
Gozala
Flaky test
help wanted
Seeking public contribution on this issue
status/ready
Ready to be worked
#302
opened Mar 10, 2021 by
achingbrain
We should fix all the @ts-ignore's introduced by #261
need/triage
Needs initial labeling and prioritization
#273
opened Nov 27, 2020 by
Gozala
Remove dependency on Ready to be worked
cid.prefix
property
status/ready
#244
opened Aug 7, 2020 by
Gozala
Improve resilience of findAndConnect
effort/hours
Estimated to take one or several hours
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
kind/bug
A bug in existing code (including security flaws)
need/triage
Needs initial labeling and prioritization
P3
Low: Not priority right now
status/ready
Ready to be worked
#226
opened Jun 5, 2020 by
jacobheun
What is the purpose of the promptedNetwork logic?
kind/support
A question or request for support
status/ready
Ready to be worked
#182
opened Sep 4, 2018 by
jacobheun
performance tests: define a baseline
status/ready
Ready to be worked
#173
opened Apr 16, 2018 by
pgte
feat: .getMany: improve performance for many small blocks
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
#163
opened Jan 27, 2018 by
pgte
Create better documentation for bitswap + webpage for it
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
#21
opened Jun 20, 2016 by
jcalfee
Document bitswap
exp/wizard
Extensive knowledge (implications, ramifications) required
help wanted
Seeking public contribution on this issue
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
topic/docs
Documentation
#18
opened May 30, 2016 by
jbenet
ProTip!
Add no:assignee to see everything that’s not assigned.