#linuxcnc-devel | Logs for 2013-12-01

[06:02:43] <KGB-linuxcnc> 03Norbert Schechner 05master 6734411 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_2 - bugfix entering the edit mode/page * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6734411
[06:13:31] <norbert> Halo, I just made my second push, the push went through, but I got the following error:
[06:13:33] <norbert> Pushing to ssh://norbert@git.linuxcnc.org/git/linuxcnc.git
[06:13:33] <norbert> remote: git_buildbot: ERROR: Could not connect to buildbot.linuxcnc.org:5133: User timeout caused connection failure.
[06:13:33] <norbert> remote: warning: refname 'bdi-4' is ambiguous.
[06:13:33] <norbert> To ssh://norbert@git.linuxcnc.org/git/linuxcnc.git
[06:13:35] <norbert> bc52acc..6734411 master -> master
[06:13:37] <norbert> updating local tracking ref 'refs/remotes/origin/master'
[06:13:49] <norbert> Did I make again something wrong
[08:16:31] <KGB-linuxcnc> 03Norbert Schechner 05master 1d81cfd 06linuxcnc 10share/gscreen/skins/gmoccapy/gmoccapy_handler.py 10share/gscreen/skins/gmoccapy/release_notes.txt gmoccapy_0_9_9_3 - fixed two smal bugs related to make a new file * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1d81cfd
[08:37:18] <cradek> norbert: no, those errors are not your fault
[08:37:40] <norbert> Thanks, I am glad for that!
[08:38:01] <cradek> norbert: the first just means the git server could not contact the buildbot server (they are far apart)
[08:38:27] <cradek> the second is a mystery to me...
[08:38:59] <norbert> Is there somethink, I can do to fix that ones?
[08:39:08] <norbert> Or at least help
[08:39:20] <cradek> the bdi-4 error? no just ignore it...
[08:39:39] <norbert> Ok, I will close my eyes ;-)
[08:40:15] <cradek> I suspect that is from the cvs import (maybe a branch and tag with the same name?) and a recent git upgrade made it appear
[08:40:27] <cradek> but that's only a wild guess
[08:43:16] <norbert> Before that push, I just cloned git, and compiled everything, and made the small changes
[08:44:41] <cradek> I am sure you didn't cause it, it is a server problem
[08:45:21] <cradek> you don't get a new clone every time, do you?
[08:45:57] <cradek> bbl
[08:46:16] <norbert> No, I just did that, because after my first push I caused a mess on the server, so I wnated to start from a clean one
[09:56:08] <jepler> "remote: warning: refname 'bdi-4' is ambiguous."
[09:56:12] <jepler> we have both a tag and a branch called bdi-4
[09:56:29] <jepler> but why git push would feel the need to bring that up I do not know
[09:57:01] <norbert> OK, so I will just go on ignoring that one
[09:57:10] <jepler> I have never seen it say this to me
[09:57:31] <norbert> OK, that advice me, what I should check?
[09:57:56] <norbert> Or I give you the right to log in on my computer if you like
[09:58:46] <jepler> Have you set this git configuration item? git config --global push.default current
[09:59:13] <norbert> No
[10:00:08] <norbert> Done now!
[10:00:10] <jepler> I recommend this setting, which causes git to only push your current branch
[10:00:30] <jepler> I have an inkling that it might be related to a warning about a branch that exists but which you do not intend to push, but I'm not sure of this.
[10:00:45] <jepler> anyway, that's a one-time setting that will apply to all of your repositories
[10:01:14] <norbert> I only got one branch on that git, I got an other git repo, where I make all my testing
[10:01:42] <norbert> I do the push, using git gui, is that a problem?
[10:01:53] <jepler> I never do pushes in git gui, but that is a personal preference.
[10:02:26] <norbert> Ok, next time I will try to push from the terminal and see if there are again that error
[10:02:59] <jepler> though if there is no "dry-run" option in git gui (I don't see it), then I do think it is bad because it doesn't let you verify what is about to happen...
[10:03:59] <norbert> Not exactly correct, if I open git gui, all modified files are shown and I can check all the changes before pushing
[10:04:15] <jepler> "git push --dry-run" is different
[10:04:28] <norbert> Ok I will doi that one than
[10:04:38] <jepler> after committing, "git push --dry-run" shows which branch(es) will be changed on git.linuxcnc.org when you actually push
[10:04:55] <jepler> the part of git gui which lets you inspect the changes file-by-file is good too
[10:05:02] <jepler> I do think it's good to create commits in git-gui
[10:47:44] <cradek> fwiw, I just updated to git-
[10:47:59] <cradek> last night I think it was
[12:29:15] <jepler> boy building the docs can sure load down my system
[12:34:56] <KGB-linuxcnc> 03Dewey Garrett 05master bc1bc54 06linuxcnc 10(19 files in 8 dirs) make: eliminate unneeded copies * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bc1bc54
[13:33:30] <KGB-linuxcnc> 03Jeff Epler 05master 3693166 06linuxcnc 10(5 files in 5 dirs) configs: copy shared files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3693166
[13:33:31] <KGB-linuxcnc> 03Jeff Epler 05master 5b15a4e 06linuxcnc 04configs/classicladder/cl-estop/emc.var 04configs/sim/remap/rack-toolchange/rs274ngc.var 04configs/smithy/emc.var don't track var files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5b15a4e
[13:33:31] <KGB-linuxcnc> 03Jeff Epler 05master bee611d 06linuxcnc 10(6 files in 6 dirs) Improve ignores * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bee611d
[13:38:12] <KGB-linuxcnc> 03Chris Radek 05master 4d9f385 06linuxcnc 10(5 files) Remove an old config that has nothing special * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4d9f385
[13:42:22] <KGB-linuxcnc> 05tags 24b663e 06linuxcnc 03bdi4 tag 'bdi4' created * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=24b663e
[13:42:53] <KGB-linuxcnc> 05tags 24b663e 06linuxcnc 04bdi-4 tag deleted * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=24b663e
[13:45:52] <cradek> some of our "sample" configs are holdovers from when pretty much only developers used emc, and we kept our personal configs in cvs
[13:49:23] <cradek> so I politely ask all you fellow old people to also delete the ones you think are useless...
[14:37:58] <JT-Shop> the plasma-thc config has never worked when anyone tried it and it very confusing with a zillion hal connections and a road map in a odg file
[14:38:05] <JT-Shop> but it is not mine to delete
[14:38:48] <JT-Shop> I tried to use it at one time but was never sucessful even printing out the connection chart on D size paper
[15:48:21] <cradek> JT-Shop: it looks like it's for particular hardware, and had some updating in 2/2009
[17:03:41] <jthornton> there is another configuration for the same hardware IIRC that might work
[17:04:49] <cradek> I trust you if you decide any configs are no longer useful
[17:06:18] <jthornton> I've tried to help a few get it to run and no luck
[17:06:31] <jthornton> I could not even get it to work
[17:06:35] <jthornton> for myself
[17:07:20] <jthornton> IIRC a guy in Iceland created it and used it to make a steel sail boat to escape Iceland
[17:08:36] <cradek> maybe we'll hear from him in july when the internet lines thaw for a few weeks?
[17:08:45] <jthornton> however interesting if you create a python decimal NaN and assign it a number it changes to an int
[17:08:48] <cradek> (yeah I remember dallur - wonder how he's doing)
[17:08:57] <jthornton> I think his plan was to leave Iceland
[17:09:09] <jthornton> I've not seen him in a long time
[17:11:59] <jthornton> I hope dallur is sailing around the world and enjoying life
[18:18:24] <dgarr> what if there was a configs/declining directory and we put doubtful configs there ?
[18:19:20] <dgarr> for eventual deletion if no claimers
[19:56:04] <cradek> if we merge ja4, all the configs will be even more out of date (i.e. totally broken)
[19:58:20] <cradek> I also think the first-run-is-baffling problem is important - sim configs (the only ones that'll work on the first run) are really quite well hidden among the majority that don't work at all (they just give some weird error or other and fail to start)
[20:00:46] <cradek> I don't know what the answer is. some nice hal examples are surely useful. having only options that work on the first run is useful too. maybe the samples should be somewhere else completely? the wiki?
[20:05:13] <cradek> I guess moving them all into a subtree and letting them languish further (and making sim on the top of the list? and renaming sim to be more descriptive?) could fix the first-run-is-baffling problem
[20:05:38] <cradek> seb_kuzminsky: ?
[20:51:56] <skunkworks> I wonder where he is?
[20:52:11] <skunkworks> ;)
[20:52:38] <skunkworks> (well - that makes it sound like I know where he is.. I don't but I assume it is life in general)