Question thread #9

[pauamma]

It's been way too long since the last question thread (why didn't anyone poke me?) so let's have another one!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer.

Comments

[metawidget]

I'm kind of terrified of switching over to Git, but I would like to fix a bug in it before too long. Is there a step-by-step resource that will help me ease into it as it's used on DW? Bonus points if it tells me how to get BBEdit in on the game.

[ninetydegrees]

Is http://wiki.dwscoalition.org/wiki/index.php/Moving_your_Dreamwidth_installation_to_use_Github relevant to you?

Edit: there might be parts of http://wiki.dwscoalition.org/wiki/index.php/Newbie_Guide_for_Windows_Users which could help you too.

Don't know where you're at and what you need so sorry if that doesn't help.

[metawidget]

Getting the move done should help me build some confidence, at least, and I can translate from Windows to Mac well enough: that second link should be helpful in getting the hang of Git basics. Thanks for the pointers!

[jewelfox]

Here is some stuff that I and the other OPW interns used for working with git. It's just the very basics though.

It also covers some stuff specific to our project, but you can just skip over that to where it says how to commit stuff and suchlike.

[denise]

the canonical git resource is Pro Git! there are a few other links on the dev getting started page.

[ninetydegrees]

Also found another one while poking around the wiki: http://wiki.dwscoalition.org/wiki/index.php/Editor:_BBEdit

[kimira]

Tried submitting a patch for the first time in a while and ran into some odd problem with git. When I tried to push to my github repo it tells me: "fatal: The remote hung up unexpectedly" and then the branch does not show up in my list of branches on github.

I think I might have also seen some kind of similar error when I was updating my code before creating the branch earlier tonight, but right after that it said "Everything up-to-date" so I thought it was okay? But apparently not.

I don't really know what this error means or how to deal with it.

[denise]

what do you get with "git push -v"?

[kimira]

Counting objects: 5419, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1239/1239), done.
POST git-receive-pack (chunked)7)
error: RPC failed; result=22, HTTP code = 411
fatal: The remote end hung up unexpectedly
Writing objects: 100% (4687/4687), 2.94 MiB, done.
Total 4687 (delta 3425), reused 4677 (delta 3415)
fatal: The remote end hung up unexpectedly
To http://kimira@github.com/kimira/dw-free.git
= [up to date] bug1514/navstripchooser_css -> bug1514/navstripchooser_css
= [up to date] bug4004/embeds_in_comments -> bug4004/embeds_in_comments
= [up to date] bug4298/advancedcustomization_link -> bug4298/advancedcustomization_link
= [up to date] bug4704/pollerrormsg -> bug4704/pollerrormsg
= [up to date] bug4708/adduser_buttons -> bug4708/adduser_buttons
= [up to date] bug791/poll_styling -> bug791/poll_styling
updating local tracking ref 'refs/remotes/origin/bug1514/navstripchooser_css'
updating local tracking ref 'refs/remotes/origin/bug4004/embeds_in_comments'
updating local tracking ref 'refs/remotes/origin/bug4298/advancedcustomization_link'
updating local tracking ref 'refs/remotes/origin/bug4704/pollerrormsg'
updating local tracking ref 'refs/remotes/origin/bug4708/adduser_buttons'
updating local tracking ref 'refs/remotes/origin/bug791/poll_styling'
Everything up-to-date

So more similar errors, it seems. :(

[denise]

hm. well, that's outside my very limited troubleshooting skill, and fu is having internet problems so she can't come help fix it for you! but i've pointed her here and she'll come help once her internet is back (or if somebody else wanders by who knows the answer, by all means!)

[kimira]

Cool, thanks for pointing help my way. :)

[denise]

although, i did a bit more looking and found a possible explanation on a google search:

http://www.btaz.com/misc/fatal-the-remote-end-hung-up-unexpectedly/

so it looks like you used the http version of the url instead of the https. fu says to read over Moving_your_Dreamwidth_installation_to_use_Github on the wiki, and redo the "git remote add" command for dw-free, with the https version instead of http?

[kimira]

Weird, I have used it since the switch to github and never had a problem before. I just followed the instructions in the newbie windows guide on the wiki, which I also followed this time. Although it has been several months since the last time I was on it so I don't know if something changed since then. Will try this...

It won't let me do git remote add because remote dreamwidth already exists... But I tried it with git remote set-url and that didn't give me an error at least.

Ahhh, but then when I tried to run the dwu script, seems I'm getting that error still:

Switched to branch 'develop'
From https://github.com/dreamwidth/dw-free
* branch develop -> FETCH_HEAD
Already up-to-date.
Switched to branch 'master'
From https://github.com/dreamwidth/dw-free
* branch master -> FETCH_HEAD
Already up-to-date.
Password for 'http://kimira@github.com':
Counting objects: 5452, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1229/1229), done.
error: RPC failed; result=22, HTTP code = 411
fatal: The remote end hung up unexpectedly
Writing objects: 100% (4654/4654), 2.93 MiB, done.
Total 4654 (delta 3403), reused 4643 (delta 3392)
fatal: The remote end hung up unexpectedly
Everything up-to-date

[denise]

hm. okay, now we're really past my knowledge! i will put up the bat-signal :)

[kimira]

Wait, think I may have figured it out. At least it worked for dwu without throwing that error so I'll see if it works for the branch push as well. From that post you linked I did "git config --list" and noticed that the remote.origin.url also wasn't https, so changed that one also and then it didn't give me that error.

Worked. for the branch push too! Yay.

[afuna]

Oh hey try opening up $LJHOME/.git/config. Look for all instances of http://... And change them to https:// manually :) should be fine after they

[kimira]

Ha thank you, yup, that was the problem. That blog post denise linked helped me figure it out. Although this would have been an easier way of changing it instead of looking up what commands I had to use. XD

[swaldman]

Yeah, git just loves its config commands, when editing the files tends to be simpler ;-)

[afuna]

Heeheehee. Glad it all worked out!