Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to "Export This Version" in Qri Desktop #1161

Closed
VarsMolta opened this issue Mar 8, 2020 · 2 comments · Fixed by #1230
Closed

Unable to "Export This Version" in Qri Desktop #1161

VarsMolta opened this issue Mar 8, 2020 · 2 comments · Fixed by #1230
Assignees

Comments

@VarsMolta
Copy link
Contributor

When I try to export a qri cloud dataset in the Qri Desktop tool, it doesn't seem to work. The directory where I tried ti export is still blank.
Using Qri Desktop v0.4.0

@b5
Copy link
Member

b5 commented Mar 11, 2020

Thanks so much for filing @VarsMolta, and apologies for the delay in responding sooner. We'll take a look & report back in the next day or two

@b5 b5 self-assigned this Mar 11, 2020
@mydogspies
Copy link

I have exactly the same problem. Also using 0.4.0. I am on Windows 10, Enterprise with no AV's other than Defender, no special permission settings or anything out of the ordinary. Tried to save to various locations including other mounted physical drives. Does Qri produce a log file I can post maybe?

b5 added a commit that referenced this issue Mar 31, 2020
Export has been failing with 'merkledag: not found' thanks to the common culprit of ds.Viz.RenderedPath
not being stored within the underlying dag. To properly fix this, we should instead fix & test the
renderedPath problem, but many datasets have been created with this issue already.

This commit supresses the error generated by referencing a path not found in ds.Viz.RenderedPath,
which has the effect of fixing export.

closes #1161
@b5 b5 closed this as completed in #1230 Mar 31, 2020
b5 added a commit that referenced this issue Apr 20, 2020
this was an incomplete fix to #1161

while running qri connect we need to properly handle the context deadline for a missing
viz by ignoring the error.
b5 added a commit that referenced this issue Apr 20, 2020
this was an incomplete fix to #1161

while running qri connect we need to properly handle the context deadline for a missing
viz by ignoring the error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants