-
Notifications
You must be signed in to change notification settings - Fork 0
📝 Overhaul the Vitessce guide
#48
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
base: main
Are you sure you want to change the base?
Conversation
|
Apparently this does not work: but if I retrieve another vitessce.json from the instance, load works and even parses the json correctly: @falexwolf do you think this should be fixed? I will use a workaround for now but this should be discussed. |
|
This artifact does not have a working widget. |
Thanks for spotting! Yes, this should be a very simple fix in There should be logic for a "freshly created artifact", but maybe it's not triggering because It's probably better if I look through this. |
|
I looked through the failing lines again and fails on CI, too, but works fine if I run it locally. I don't get it. |
|
Can you share a full traceback? Because now I'm pretty confused 😅 -- I thought it was just about an artifact that hadn't yet been saved to the database. |
|
@falexwolf please have a look at the CI error, it is doing the weird thing again. |
|
Looking! |
|
Ok, that's a very clear error We do support So, it'd be trivial to get We just need to also map The question is: Why does this work for you locally? |
|
@falexwolf this is so weird. I just ran the code from my screenshot again and it threw the |
|
Thanks for making the PR! Strange that it ever worked. It should never have worked. This is very simple code. 😅 |


WIP