qri get will only return an empty object

[osterbit]

• get the same result whether I provide a path (like qri get meta) or without one
• link to the dataset.yaml and body data.json in a gist
• I tried including the full path as mentioned in bug: unable to get datasets using just peername/datasetname #479 but get same result

[dustmop]

Try patching in the branch from #505

[dustmop]

I tried to create my own version of the dataset using: qri add --file=dataset.yaml --body=data.json me/test_repo, and qri get meta works fine. This implies there's something specific to the particular instance of the dataset.

[dustmop]

When I try to get the contents of the same dataset that @osterbit was speaking about, I get an entirely different error:

> qri get meta color_dog2/paris_energy_pledges3
error loading dataset: error getting file bytes: error resolving hash: selected encoding not supported

Going to investigate.

[dustmop]

More info:

When I ran qri add color_dog2/paris_energy_pledges3 to add the dataset to my repo, then qri get color_dog2/paris_energy_pledges3 would work properly for me.

On @osterbit's end, running qri use color_dog2/paris_energy_pledges3 followed by qri get would properly get the data. I think this is a duplicate of #492?

[dustmop]

Talking with @osterbit, this appears to be fixed now, indeed with the same root cause as #492.