Asmir Avdicevic

range reqs https://github.com/n0-computer/iroh/pull/330

Missing 404 handling / templates for completion.

a bunch more like this ```Oct 17 14:10:29 ip-172-31-82-125 teststream[226969]: REZ: 500 | g-dig | {"code":500,"message":"unexpected unixfs type Some(File)","success":false,"trace_id":"00000000000000000000000000000000"} | http://g1.gateway.lol:9050/ipfs/bafybeigy6zyjllz3lsbu5exsrgks54utgsvuvddphaytrbmypevya7lkuy%2F```

``` Oct 20 13:47:05 ip-172-31-82-125 teststream[249059]: REZ: 500 | g-dig | {"code":500,"message":"Expected Key(\"\") but found Bytes","success":false} | http://g1.gateway.lol:9050/ipfs/bafkreiepsojuhcfji7wwdy2npx7egyhi66aknogiklq35hiurynedw3fuu%2F Oct 20 13:47:05 ip-172-31-82-125 teststream[249059]: REZ: 500 | g-dig | {"code":500,"message":"Expected Key(\"\")...

Appreciate the thorough feedback here. It also highlights our need to revamp/update a lot of our error handling to make it more user friendly. The `qri validate` suggestion is a...

``` $> qri log 1 Commit: /ipfs/QmVx438tG5FZLM2xLaz9YD57RPSVhDR2fFv8QfaDuGRaok Date: Wed Jun 10 11:20:46 CEST 2020 Storage: local Size: 110 kB created dataset ``` ``` $> qri status for linked dataset [koka/population_bank_world]...

I was manually re-doing my user but kept the .ipfs folder around. I'd say the probably biggest culprit is tons of the same user settings recreated while testing a local...

So I'm re-opening this as I've managed to encounter this with an empty repo. Here's a branch that logs out the following (`--log-all`) https://github.com/qri-io/qri/commit/217b8dbd99b8a84c8c09c59124468d737f26bcba ``` $> qri save for linked...

So got another update on this. I can reliably reporduce this from a fresh repo. If the initial body is: ``` one,two,3 four,five,6 ``` And I update it to: ```...

Just to add newer info, seems like if I do `qri save` any number of times it fails. However if I do `qri status` and then `qri save` it picks...