Dustin Long

I ran into the same problem. Worked around it by running `go get github.com/russross/blackfriday/v2@3e56bb68c8876389c631e9e318ce3c092a0906db`, where `3e56bb68c8876389c631e9e318ce3c092a0906db` is the most recent git commit on the v2 branch, then using the import...

Building from source, however, and then running works ok (after upgrading to rust 1.54.0). Apologies for the noise, feel free to close if this is expected behavior.

I am unable to reproduce this in Windows. When I have a dataset that isn't checked out, the "Show in explorer" option is disabled.

This is a consequence of https://github.com/qri-io/qri/issues/1483, and we need to fix logbook in order to make this work correctly.

Just to make sure we're on the same page, LogItem does not *contain* a VersionInfo, it *embeds* a VersionInfo. So we won't have: ``` LogItem = { "versionInfo": { "name":...

Question about this. We basically defined `VersionInfo` as "what `qri list` needs to display its results", with the near future plan that dscache would store exactly a list of `VersionInfo`....

Can't reproduce on Windows, I think this issue is something going wrong in the backend without the error being handled properly. We need better logging in the backend in order...

Sure, I think we should go forward with trying AppImage. The other alternative is Flatpak, but I don't have enough information to really judge which is preferred. Do we know...

Still getting "logbook: not found" for certain datasets, but not getting "reference not found" anymore. ``` > qri get xristosk/bot_sentinel_trolls logbook: not found > qri get mfdz/stuttgart_gelbekarten pulling mfdz/stuttgart_gelbekarten from...

Figured out part of this problem, `qri pull` used to not add logbook data to your own repo, so when we try to locally resolve such a reference, there's no...