-
Notifications
You must be signed in to change notification settings - Fork 13
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
Cannot publish on staging due to "invalid" URL #961
Comments
ping on this @waxlamp @dchiquito et al |
Thanks @yarikoptic; looking into it. |
@waxlamp any updates on this? |
The root of this issue is in dandischema, as there we check that the version url is as expected. However, currently this only accounts for the main deployment ( It seems to me the approach to fix this is to either add the staging url to that regex, or to change the behavior in dandischema to instead read the value of an environment variable (e.g. I prefer the second approach. |
… needed Ref: dandi/dandi-archive#961 I have decided to not hardcode gui-staging. one because the fix is targetting specifically dandisets testing, and otherwise AFAIK is not needed elsewhere. If something wants to upload to staging, they can also adjust their CI to point to whatever instances they upload to
thanks @AlmightyYakob . I haven't analyzed why it started to happen, and followed your recommendation to propose dandi/dandi-schema#128 . I guess let's continue on that particular possible fix there edit: forgot to mention relevant somewhat dandi/dandi-schema#67 |
It probably started to occur as a result of #946 |
might be, might be ... thanks @AlmightyYakob for pointing that PR out since I was wondering. Indeed many moving parts and even though integration test of |
This was resolved some time ago. |
Dandisets on staging currently fail validation with:
The text was updated successfully, but these errors were encountered: