-
Notifications
You must be signed in to change notification settings - Fork 86
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
[Exit Status 128] - Nbgitpuller Doesn't Allow Access to R.Datahub #327
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
@paulamarm I think this solution would fix this issue. You can also check the solution provided for a similar issue faced by a Berkeley instructor. |
I recognize that this is usually a merge issue but I haven't made changes post-uploading to github in many assignments/weeks and the student also mentioned that they doubt opening the assignment anytime soon after it was released. |
@paulamarm I think this can be solved more easily by troubleshooting the students' server. I have reached out to you via Slack to get the student's calnet id so that I can log into their servers and do the necessary troubleshooting. |
@paulamarm confirmed over Slack that this issue was resolved. Renaming the user file seemed to do the trick. |
Bug description
Hi, I'm experiencing the same bug as issue #153 for one student. They see the same nbgitpuller error when they open the datahub and I'm wondering what files I should be trying to fix in her downstream data hub to fix this issue, since I can open her datahub even though she is getting this issue.
How to reproduce
See error:
Your personal set up
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: