Skip to content
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

flag issue to binderhub about ucla dvn not working with mybinder #21

Closed
jt14den opened this issue May 24, 2020 · 3 comments
Closed

flag issue to binderhub about ucla dvn not working with mybinder #21

jt14den opened this issue May 24, 2020 · 3 comments
Assignees

Comments

@jt14den
Copy link
Contributor

jt14den commented May 24, 2020

add issue to https://github.com/jupyterhub/binderhub that the binder build from dataverse doi not working for us. See the PR: jupyterhub/binderhub#969

Currently when we plug a DOI into mybinder with Dataverse DOI selected, the build holds at "wait" and never moves forward.

Curiously, Zenodo will build container, but the share URL will not work.

@jt14den jt14den changed the title add issue to https://github.com/jupyterhub/binderhub that the binder build from dataverse doi not working for us. See the PR: https://github.com/jupyterhub/binderhub/pull/969 flag issue to binderhub about ucla dvn not working with mybinder May 24, 2020
@jt14den
Copy link
Contributor Author

jt14den commented Jul 27, 2020

@jmjamison I haven't tested this in awhile. Can you see if it still isn't working?

@jmjamison
Copy link

Tested this morning and it's still stuck at 'waiting to build'.
I've put in an issue: jupyterhub/binderhub#1133

@jmjamison
Copy link

Re: jupyterhub issue #1133, the response was that it was a dataverse issue not a jupyter/binder issue. Dataverse support response was that it should work.
I went back to test a SSDA DOI on Harvard dataverse and that worked. Then I tried a recent UCLA dataverse DOI (https://doi.org/10.25346/S6/DE95RT), more than once. The first time was quite slow but subsequent run used the now existing image in the docker repo.
In conclusion I don't know why it started working. There could have been changes that I'm not aware of. For now I"m going to close this issue as hypothetically fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants