search

qri-io / desktop

Qri Desktop
https://qri.io/desktop
GNU General Public License v3.0
67 stars 14 forks source link

I can only see/work on 1 dataset at a time #356

Closed amandabNYC closed 4 years ago

amandabNYC commented 4 years ago

I cannot see the history of datasets I've created in Qri - I can only see in the most current dataset I've worked on the the status bar.

Qri4 Qri5
chriswhong commented 4 years ago

Can you tell me what you see when you type qri list in a command prompt?

dustmop commented 4 years ago

Hi @amandabNYC, sorry for the delay in responding to this issue. I'm going to be taking a look at this early next week to try and help you out.

This is running on Windows, right? When you get a chance, could you open the app and do the following:

  1. press the keyboard shortcut "Ctrl+Shift+I (capital i)" to open Developer Tools
  2. click the "Console" tab
  3. screenshot or copy-paste the contents into this issue

That would help us diagnostic what the issue is that's causing Qri Desktop to not work correctly.

Here's an example of what this looks like on my machine: qri_example_win

amandabNYC commented 4 years ago

I don't have command prompt access - I am working from a PC. I don't know if that makes a difference.

On Wed, Dec 4, 2019 at 3:36 PM Chris Whong notifications@github.com wrote:

Can you tell me what you see when you type qri list in a command prompt?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/qri-io/desktop/issues/356?email_source=notifications&email_token=AJ7QXVPE5R4CW7E4X4VA4Q3QXAIDNA5CNFSM4JURX3W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF6NAPI#issuecomment-561827901, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ7QXVNCRFADN63FXCTYI73QXAIDNANCNFSM4JURX3WQ .

amandabNYC commented 4 years ago

See attached for screenshot:

On Fri, Dec 6, 2019 at 4:40 PM Dustin Long notifications@github.com wrote:

Hi @amandabNYC https://github.com/amandabNYC, sorry for the delay in responding to this issue. I'm going to be taking a look at this early next week to try and help you out.

This is running on Windows, right? When you get a chance, could you open the app and do the following:

  1. press the keyboard shortcut "Ctrl+Shift+I (capital i)" to open Developer Tools
  2. click the "Console" tab
  3. screenshot or copy-paste the contents into this issue

That would help us diagnostic what the issue is that's causing Qri Desktop to not work correctly.

Here's an example of what this looks like on my machine: [image: qri_example_win] https://user-images.githubusercontent.com/2515490/70358313-13abeb00-1847-11ea-8d9e-5f9a79ae46e9.PNG

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/qri-io/desktop/issues/356?email_source=notifications&email_token=AJ7QXVIW5ZFG5CUXVRX3JGTQXLBGFA5CNFSM4JURX3W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGFNNJQ#issuecomment-562747046, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ7QXVI6JYCVIKJDMA6S2TTQXLBGFANCNFSM4JURX3WQ .

ramfox commented 4 years ago

hi @amandabNYC ! I think when you replied to the email, the screenshot was lost. Mind heading over to https://github.com/qri-io/desktop/issues/356 and posting the screenshot again :)

dustmop commented 4 years ago

I watched the video from the recent meeting where this came up. It helped a bunch! Here's what I got from it:

1) Was able to figure out the cause of the "Oops, something went wrong with this commit" message. Our backend requires that dataset names start with a letter, so the name "911calls" won't work. We have to make sure that our rules about what dataset names are valid are consistent, and desktop needs to be both checking the dataset name and also handling errors better.

2) But something was going wrong with Desktop even before that. When @amandabNYC clicked on "Create Dataset" in the "Create a New Dataset" dialog box, the app makes a call to "/init", and waits for it to return, but afterwards the dialog box doesn't close. What's weird is that it didn't get an error. This seems to be the root of the other problems, including the right-hand pane showing multiple views at once.

3) I could theorize about what's going wrong here, but we really need better logging for desktop to gather data about what part specifically is breaking. We're probably not handling some error somewhere. Would be cool if a user could click a "download log" button somewhere that would save a logfile that could then be emailed to us.

4) Our recent UI redesign is going to remove this flow, meaning it may not even be possible to recreate going forward. Whatever this specific error case was, it might just disappear.

amandabNYC commented 4 years ago
Qri6

I'm not sure if this is still relevant or not, but see attached.

I haven't had a chance to use the updated version as of yet. I will apprise of any new/continuing issues once I'm back on wi-fi.

chriswhong commented 4 years ago

I believe these should be addressed in newer releases. Please re-open if you're still seeing the issue.