-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Level 28. Push - No remote - File name too long. #201
Comments
This looks the same as #188 which I closed because I couldn't replicate it. Could you please provide: Operating System Thanks. |
I too am running on cloud9. And yes same exact thing. I ended up with a seemingly infinite series of nested folders called d20160118-12089-1bn4nyx or some variation. Each had an empty 'file1' inside along with another folder of the same name. Cloud 9 is running: |
I sent you an invite to the c9 workspace so you don't have to try replicating it. |
@dukeoflaser That's fantastic, from that I should at least be able to see the issue for myself. I'll investigate it tomorrow. Thanks for setting this up. |
After a quick look - https://github.com/Gazler/githug/blob/master/levels/push.rb#L10 appears to be the offending line. |
Alright, I've tracked down the issue thanks to the provided workspace. There are two things at play here:
|
@dukeoflaser I am done with that workspace now by the way. Thanks again for setting it up. This should be fixed in 0.4.8 |
Great thanks! I look forward to giving it another try 👍 |
When I first run/reset level 28 I get an error with a massive string of characters.
...fileutils.rb:1392:in `initialize': File name too long @ rb_sysopen - ... 117-5586-1s8nzqj/d20160117-55 ...etc. ... (Errno::ENAMETOOLONG)
Any attempt at solving it, ex: git rebase origin/master master, results in:
=>fatal: Needed a single revision
=>invalid upstream origin
git remote:
Does not display any remote repos.
git pull origin master:
=>fatal: 'origin' does not appear to be a git repository
=>fatal: Could not read from remote repository.
=>Please make sure you have the correct access rights
=>and the repository exists.
The text was updated successfully, but these errors were encountered: