-
Notifications
You must be signed in to change notification settings - Fork 8
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
Unexpected Error when pulling submodules (notebooks) #41
Comments
Hey @T4mmi , we are just getting to these now - Gautier got in touch and I suggested the following fix
as opposed to recures-submodule without the 's'. Is this all good now? |
nice addition, this should do ... but I still have an unexpected error trying to pull submodules (notebooks) ... |
To make sure you don't lose any work, do a git status and copy over anything you've changed, or git stash --keep-index. And then remove the submodule directories and check out this post - https://stackoverflow.com/a/1032653/8490364 - it should just be a
|
Weirdly, It still crashes without notice or traceback/log (only Git GUI frontend gives me a unexpected error...) ...
works where
does not .... and I can't explain it so i'll just leave it here in case anyone faces the same problem ... |
There's likely old stuff lurking in the .git directory. Try git rm map2loop2-notebooks && rm -rf .git/modules/map2loop2-notebooks. Then change the .gitmodules entry back to map2loop2-notebooks and init submodules again. Or leave it as is, not sure it matters that much, haha I will leave this open though, let me know if there are any more issues. |
I suspect there is indeed something lurking inthe but the [edit] but maybe wait and see if someone else has the same issue to spend time on this, it might just be my setup that is messy :) |
Hi,
Thanks for refactoring of the repo, we have trouble pulling submodule (
map2loop2-notebooks
).It throws an unexpected error without log/traceback.
Nothing blocking but might require a very little patch.
this is more of a feedback than an issue...
The text was updated successfully, but these errors were encountered: