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

[Exit Status 128] - Nbgitpuller Doesn't Allow Access to R.Datahub #327

Open
paulamarm opened this issue Oct 5, 2023 · 5 comments
Open
Labels

Comments

@paulamarm
Copy link

paulamarm commented Oct 5, 2023

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

  1. Go to the course website and access datahub using the nbgitpuller link (https://publichealth.datahub.berkeley.edu/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Fph142-ucb%2Fph142-fa23&urlpath=rstudio%2F&branch=main)
    See error:
Screenshot 2023-10-05 at 11 29 17 AM

Your personal set up

  • OS:
  • Version(s):
Full environment
# paste output of `pip freeze` or `conda list` here
Configuration
# jupyterhub_config.py
Logs
@paulamarm paulamarm added the bug label Oct 5, 2023
@welcome
Copy link

welcome bot commented Oct 5, 2023

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@balajialg
Copy link

balajialg commented Oct 5, 2023

@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.

@paulamarm
Copy link
Author

paulamarm commented Oct 6, 2023

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.
Every file I uploaded that week showed merge behavior on the student's github, but since there are so many files and I was able to export their submission I simply deleted the files that had been duplicated or released by that point. The student still has the same issue so I think it's either device-related or something I'm missing at this point in the student's files/ the commit history.
(https://publichealth.datahub.berkeley.edu/user/andreamald4/git-pull?repo=https%3A%2F%2Fgithub.com%2Fph142-ucb%2Fph142-fa23&urlpath=rstudio%2F&branch=main&redirects=1)
Any advice?

@balajialg
Copy link

balajialg commented Oct 6, 2023

@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.

@balajialg
Copy link

@paulamarm confirmed over Slack that this issue was resolved. Renaming the user file seemed to do the trick.

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

No branches or pull requests

2 participants