Unfetchable root

[rvagg]

bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 appears to lead to a black hole. Returns a CAR with it listed as the root but no body.

curl -v -H 'Accept: application/vnd.ipld.car;version=1;order=dfs;dups=y' 'https://dag.w3s.link:443/ipfs/bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4?dag-scope=block' -o w3s.car 

Lots of failing requests trying to path from this block:

 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /15626?dag-scope=entity&car-scope=file |   8
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /27131?dag-scope=entity&car-scope=file |   7
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /20209?dag-scope=entity&car-scope=file |   7
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /6673?dag-scope=entity&car-scope=file  |   7
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /17496?dag-scope=entity&car-scope=file |   7
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /19824?dag-scope=entity&car-scope=file |   7
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /12807?dag-scope=entity&car-scope=file |   6
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /34743?dag-scope=entity&car-scope=file |   6
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /10339?dag-scope=entity&car-scope=file |   6
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /29025?dag-scope=entity&car-scope=file |   6
 bafybeidu5wtgjfakk6q7uyykhf2225bko4wlgrug5m6x3pabtanopolsg4 | /441?dag-scope=entity&car-scope=file   |   6
...

[alanshaw]

Known issue - this is a CAR that hasn't been moved into Cloudflare R2 just yet.

[rvagg]

Same issue with bafybeihkbmy5eajjtg42b4auzxcpheksf5pt5bojnm4zr4ba36jwwtfbmi? Lots of paths such as /9816.json, /9225.json, /8337.json. I can curl with just the CID and get the root block, a unixfs shard, but dag-scope of entity or all doesn't get me anything more than the root.

[rvagg]

Not sure if this is helpful but here's some more:

• bafybeigp4tbtictgbwgeqv4vni4yeqd6nqmibthikhnrhnw3smk3liqw54 -> /78899.json, /78959.json, /80236.json
• bafybeihaseo2mkbd6marsulwtfvrr4626oed55xmy5bl5cqfdxghfhnk64 -> /13623.json, /9185.json, /14064.json
• bafybeidthw2pfvded5ieu64lyc6woantxfpv72eppivwzfjbnhazli4eu4 -> /399.json, ``/1881.json, /4028.json`
• QmVFh1a8w6t7gUgJkwuV4jZfdmf73FHtNcQgAsDkwpQGa6 -> /231399.json, /232360.json, /217006.json

I've confirmed at least QmVFh1a8w6t7gUgJkwuV4jZfdmf73FHtNcQgAsDkwpQGa6/231399.json resolves properly via bitswap, so at least one of the paths above is valid but unfetchable.