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
It appears that when using the client, if the access of a dandiset fails for any reason (doesn't exist, embargoed without access, version string is wrong, etc.), then immediately navigating to a dandiset which is accessible through the "public dandisets" page fails and raises a bunch of errors. This is seemingly due to carried over state, and its interaction with the meditor. Steps to reproduce:
It appears that when using the client, if the access of a dandiset fails for any reason (doesn't exist, embargoed without access, version string is wrong, etc.), then immediately navigating to a dandiset which is accessible through the "public dandisets" page fails and raises a bunch of errors. This is seemingly due to carried over state, and its interaction with the meditor. Steps to reproduce:
The reason I say it's connected to the meditor is because I observed the following console error:
Cannot destructure property 'modelValid' of 'editorInterface.value' as it is null
The text was updated successfully, but these errors were encountered: