Search results

Tests should not use ipfs

exp/noviceSomeone with a little familiarity can pick upSomeone with a little familiarity can pick up

help wantedSeeking public contribution on this issueSeeking public contribution on this issue

P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps up

status/readyReady to be workedReady to be worked

Status: Open.

#31 In ipfs/js-ipfs-http-response;

· vasco-santos opened on Jan 7, 2020

Sharding support in /ipns/<fqdn> paths

help wantedSeeking public contribution on this issueSeeking public contribution on this issue

kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing feature

status/readyReady to be workedReady to be worked

Status: Open.

#22 In ipfs/js-ipfs-http-response;

· lidel opened on May 6, 2019

Enable Windows CI on travis

help wantedSeeking public contribution on this issueSeeking public contribution on this issue

P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps up

status/readyReady to be workedReady to be worked

Status: Open.

#21 In ipfs/js-ipfs-http-response;

· vasco-santos opened on Apr 8, 2019

Replace manual traversal with ipfs.resolve

exp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is important

help wantedSeeking public contribution on this issueSeeking public contribution on this issue

P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps up

status/readyReady to be workedReady to be worked

Status: Open.

#14 In ipfs/js-ipfs-http-response;

· lidel opened on Jan 15, 2019

Needs the Priotity and Difficulty labels

status/readyReady to be workedReady to be worked

Status: Open.

#11 In ipfs/js-ipfs-http-response;

· daviddias opened on Aug 25, 2018

Add Suborigin, Etag and X-Ipfs-Path headers

kind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)

status/readyReady to be workedReady to be worked

Status: Open.

#10 In ipfs/js-ipfs-http-response;

· lidel opened on Aug 22, 2018

Resolve with a POJO response

good first issueGood issue for new contributorsGood issue for new contributors

kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing feature

status/readyReady to be workedReady to be worked

Status: Open.

#6 In ipfs/js-ipfs-http-response;

· satazor opened on Aug 2, 2018

Add tests that assert that the payload is correct

help wantedSeeking public contribution on this issueSeeking public contribution on this issue

kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing feature

status/readyReady to be workedReady to be worked

Status: Open.

#4 In ipfs/js-ipfs-http-response;

· satazor opened on Aug 1, 2018