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
{{ message }}
This repository has been archived by the owner on Feb 4, 2018. It is now read-only.
We've had at least one case where a build failed to finish but also never reported an error, although this shouldn't happen, we should add a catchall timeout for builds just in case, as it's frustrating to be stuck with a repo and unable to rebuild.
The text was updated successfully, but these errors were encountered:
The second one seems to be stuck in limbo, because no new log messages are generated anymore. I'm not sure how I caused it to crash, but I know that the build created a big amount of log messages, as it tried to download 4GB from a rather slow external server.
I would appreciate a timeout for the build process or perhaps even a "force rebuild" or a "cancel build" button for the user.
Thank you for the amazing work, I really love mybinder.org and will do my best to not break it again.
Best,
Michael
I also have two wedged builds that I cannot break out of. One has been in that state for three weeks. Is there any kind of manual workaround for this, however obscure? I considered renaming my repo, but since this has happened to two of the three binders I've created, I'm pessimistic about that being a useful approach.
We've had at least one case where a build failed to finish but also never reported an error, although this shouldn't happen, we should add a catchall timeout for builds just in case, as it's frustrating to be stuck with a repo and unable to rebuild.
The text was updated successfully, but these errors were encountered: