You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the dashboard I ran into and issue where my running instances weren't displayed in the UI (see attached video). When using the Girder Web API it was apparent that I did have two instances running with status 3.
I haven't found a way to reliably reproduce this, but I was using the analyze in Whole Tale feature.
I also noticed that after waiting for a few minutes, I tried to delete one of the instances via the API and the instance ID wasn't found. I re-queried for instances and found one that I had probably started earlier (but no record of the two that are in the video).
Not sure what the best way to handle this is, given the limit on running instances and the weird timing issues we've seen with deleting and refreshing/navigating in the past.
We could add a "show hidden" or "show deleting" toggle for sanity / debugging purposes, but in my head that's starting to get a bit convoluted and doesn't feel like the right answer
When using the dashboard I ran into and issue where my running instances weren't displayed in the UI (see attached video). When using the Girder Web API it was apparent that I did have two instances running with status 3.
I haven't found a way to reliably reproduce this, but I was using the analyze in Whole Tale feature.
I also noticed that after waiting for a few minutes, I tried to delete one of the instances via the API and the instance ID wasn't found. I re-queried for instances and found one that I had probably started earlier (but no record of the two that are in the video).
https://recordit.co/MkTLXbAJGC
Here's a snapshot of the recent jobs that had run
The text was updated successfully, but these errors were encountered: