#linuxcnc-devel Logs

Apr 08 2017

12:49 AM KGB-linuxcnc: 03Sebastian Kuzminsky 052.7 e6dfac4 06linuxcnc 10docs/src/code/code-notes.txt docs: a pose has 9 coordinates, not 6 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e6dfac4
02:04 AM linuxcnc-build: build #3040 of 1405.rip-wheezy-armhf is complete: Failure [4failed compile runtests] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1405.rip-wheezy-armhf/builds/3040 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Joe Hildreth <joeh@threerivershospital.com>
02:12 AM linuxcnc-build: build #4888 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4888 blamelist: Sebastian Kuzminsky <seb@highlab.com>, Joe Hildreth <joeh@threerivershospital.com>
02:19 AM seb_kuzminsky: USRMOT: ERROR: command timeout
02:30 AM seb_kuzminsky: linuxcnc-build: force build --branch=2.7 0000.checkin
02:30 AM linuxcnc-build: The build has been queued, I'll give a shout when it starts
03:42 AM linuxcnc-build: build forced [ETA 1h31m22s]
03:42 AM linuxcnc-build: I'll give a shout when the build finishes
05:51 AM linuxcnc-build: Hey! build 0000.checkin #4890 is complete: Success [3build successful]
05:51 AM linuxcnc-build: Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4890
10:38 AM Joe_Hildreth: seb: Unless I misunderstand, it looks like the master branch failed to build and you rebuilt the 2.7 branch.
10:39 AM Joe_Hildreth: and ... considering I seem to be a mistake state machine this week, that may very well be the case! :-)
10:39 AM cradek: Joe_Hildreth: you can poke the buildbot too, if you want it to do something special
10:39 AM Joe_Hildreth: cradek: what do you mean poke the buildbot?
10:40 AM cradek: give it a command over irc in this channel
10:41 AM cradek: like (I assume you're talking about) something seb did
10:41 AM Joe_Hildreth: Hmmm, I don't know anything about that. I better try to learn something about that before I try poking. Like the pitt bull my neighbor has. HAHA
10:43 AM Joe_Hildreth: I was. I added some updates to 2.7 that seb merged into master and the build failed. Looking at the IRC logs it looks like he noted that it failed and done a force rebuild or something, but from looking at the results that build was on 2.7 and not master. Unless I misunderstand.
11:54 AM seb_kuzminsky: Joe_Hildreth: you're right, master failed to build and i told the buildbot to build 2.7
11:54 AM seb_kuzminsky: in my defense i was really sleepy
11:55 AM seb_kuzminsky: linuxcnc-build: force build --branch=master 0000.checkin
11:55 AM linuxcnc-build: build forced [ETA 1h50m07s]
11:55 AM linuxcnc-build: I'll give a shout when the build finishes
12:02 PM Joe_Hildreth: seb: No I get get it. I wasn't even sure I was reading it all right. I didn't know until this morning you could poke the buildbot. I had to ask what that meant.
12:08 PM seb_kuzminsky: it can do a bunch of stuff here in irc, but the most useful by far is just starting a build
12:08 PM seb_kuzminsky: linuxcnc-build: commands
12:08 PM linuxcnc-build: buildbot commands: commands, dance, destroy, force, hello, help, last, list, mute, notify, source, status, stop, unmute, version, watch
12:30 PM Joe_Hildreth: seb: a question. You told me if I was doing a commit for an issue to put the text fixes#<issue number>. Can anything else go in the commit text or just that by itself?
12:31 PM cradek: you can say other stuff too
12:31 PM cradek: in fact, you must at least also have the signed-off-by
12:32 PM Joe_Hildreth: Thanks cradek. Do you guys prefer single line commit comments, or single line with addition detail?
12:33 PM cradek: it depends on how much explanation is needed. the important thing is that you say why you made this change. sometimes that's quick to say, other times not
12:33 PM Joe_Hildreth: so this would be fine: git commit -sm "fixes #248, removes references to Ubuntu 10.04"
12:33 PM cradek: new source control users often make the mistake of saying WHAT they changed - that's silly because you can see it right there! but what was in your head at the time? that's what's important to capture.
12:34 PM cradek: that's a good example. it would be better to say "because 10.04 is deprecated for master branch now" instead of "removed stuff"
12:34 PM Joe_Hildreth: Well, I am new and bound to make some error with the process. I am just glad that you guys are such a great resource.
12:35 PM cradek: :-)
12:35 PM Joe_Hildreth: I see.
12:36 PM cradek: sometimes the "why" even talks about a user's expectations, compatibility with a spec or another control, that kind of thing
12:36 PM Joe_Hildreth: I think I will tackle issue 58 next. The manpage for the parport component. Mostly so I get a better understanding of the component myself.
12:36 PM cradek: sweet
12:38 PM Joe_Hildreth: I at least feel like I am giving back something to the community, even if it is only dimple doc stuff.
12:38 PM cradek: docs are super important for getting new users up and running
12:38 PM Joe_Hildreth: Maybe someday I will learn enough to do something better. Have to get used to the training wheels first.
12:40 PM Joe_Hildreth: Hey, I worte a tutorial on best wiring practices a while back. I was doing it in the forum and pretty much have it finalized. Would that be a good addition to make, or would that distract from the core project?
12:41 PM cradek: hm, I don't know. I can see it both ways.
12:41 PM archivist: it is a common question in irc and not easy to explain in a few lines
12:41 PM cradek: maybe ask jt?
12:41 PM cradek: yeah
12:42 PM Joe_Hildreth: My mindset is from a newbie point of view, or perhaps a hobbiest point of view. I may be skewed.
12:42 PM archivist: people just dont get the screening and common mode currents
12:42 PM cradek: I think it should be somewhere other than the forum - maybe the wiki would be better?
12:42 PM cradek: I think forum threads aren't a good place to keep permanent documentation
12:43 PM Joe_Hildreth: If you like, I can email it to you to look at.
12:43 PM archivist: forum is bad for permanent, I have seen quite a few fails
12:43 PM cradek: I don't want to pretend to be the judge... if anyone it should be jt
12:44 PM cradek: I know he maintains a separate site for his own things that don't belong in the main docs
12:44 PM cradek: others use the wiki for that
12:44 PM archivist: I suppose I do something similar to jt and self host my bits
12:44 PM cradek: I guess I do too
12:45 PM Joe_Hildreth: Well, I wrote it because of my own problems. I was doing a tutorial on adding a touchprobe and ran into problems with noise from my crappy wiring job.
12:45 PM cradek: it sounds useful
12:45 PM Joe_Hildreth: Ask a million questions, done some research and put the doc together.
12:46 PM archivist: I am slowly playing with probe interfacing too, got the faster opto and can see the 115k now
12:46 PM Joe_Hildreth: My intention is to demonstrate the problem I am having, show my wire drawer and then rewire it, making it a series of YouTube videos.
12:47 PM cradek: that would be neat - a lot of folks ask for documentation in the form of videos
12:48 PM Joe_Hildreth: My son is my driving force. He is in school in a machinist program. He assisted in my router build and I want to teach him.
12:49 PM Joe_Hildreth: I have several people ask questions at more than the basic level. But I feel before I start spewing out stuff, that I need to really have a better grip on it than I do.
12:50 PM Joe_Hildreth: I try to remind people I am a network guy, not a programmer, or a system integrator, or a machinist. Just a hobby for me along with dabbling in metalcasting and some other junk.
12:51 PM cradek: https://en.wikipedia.org/wiki/Impostor_syndrome
12:52 PM Joe_Hildreth: HAHAHA, are you diagnosing me?? :-D
12:53 PM cradek: I wouldn't do that, I'm no expert, any correct diagnoses are just luck :-)
12:53 PM Joe_Hildreth: Gotcha. Well I do have a little electronics background. Was an ET in the navy.
12:54 PM archivist: Extra Terrestrial ?
12:54 PM Joe_Hildreth: In the computer industry, I would consider myself a jack of all trades and a master at none.
12:55 PM Joe_Hildreth: Electronic Technician.
12:55 PM archivist: I think the jack of all trades is very common to use tinkerers of cnc's
12:56 PM archivist: use/us
12:56 PM Joe_Hildreth: I manage the IT department for a hospital and am the only one. So if it is new VLAN, new WAn services, programming componenets for the internal Joomla website, etc. etc. It is all me.
12:56 PM Joe_Hildreth: Great, I must be in good company then.
01:10 PM skunkworks: heh - have a degree in electronics.. Run an IT department.. And machine for a hobby...
01:12 PM linuxcnc-build: Hey! build 0000.checkin #4891 is complete: Success [3build successful]
01:12 PM linuxcnc-build: Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/4891
01:23 PM DrippityDrops: I use the 7i90, 7i92 and 7i80 on multiple machines, is there a good reason there is not a pncconf example included for these cards? is this something that I could do and add to the next release?
01:24 PM seb_kuzminsky: DrippityDrops: i think the only reason there's no support in pncconf for those boards is because no one's added them yet
01:24 PM seb_kuzminsky: i don't know much about pncconf, there may be some other reason i don't know about
01:25 PM DrippityDrops: Oh, it seems like such an easy thing to do. Or maybe just add a sample config for each card into the linuxcnc config picker.
01:27 PM Joe_Hildreth: seb: I done a git fetch upstream on my local computer. I am not seeing the two commits, mine and yours. Do I need to do this different?
01:28 PM Joe_Hildreth: I think I had to tell git to track 2.7 branch. Do I have to do the same for upstream/master?
01:30 PM seb_kuzminsky: Joe_Hildreth: "fetch" means "go get all the new things from this remote, and put them in my local database of commits and files and things, but don't make any changes to my local branches or to the working directory"
01:31 PM Joe_Hildreth: OK, so I want to force?
01:31 PM seb_kuzminsky: after you fetch, you can look at what's new from the remote, and decide how to integrate it into your local set of branches (and thus into your local working directory)
01:31 PM seb_kuzminsky: no, no force is needed here
01:32 PM seb_kuzminsky: after the fetch, try something like "git log --graph --oneline --decorate 2.7..upstream/2.7"
01:32 PM seb_kuzminsky: that will show you the log of commits starting with your local 2.7, and going to upstream's 2.7 that you just fetched
01:32 PM Joe_Hildreth: OK, I created an issue branch from master and made my changes there, pushed and done the PR, I made sure to stay out of master when i done that.
01:33 PM seb_kuzminsky: you should see the commits you made, and the merge commits i made to accept your PRs
01:33 PM Joe_Hildreth: I see the commits when I am on branch 2.7.
01:33 PM Joe_Hildreth: I just don't see them on master.
01:33 PM seb_kuzminsky: and likewise, "git log --graph --oneline --decorate master..upstream/master" to see the commits from your local master branch to upstream/master
01:33 PM seb_kuzminsky: hmm, did i not merge it last night into master?
01:34 PM seb_kuzminsky: no, it's all in master
01:34 PM Joe_Hildreth: You did, the command you just gave shows the additional commits
01:34 PM seb_kuzminsky: ok, good
01:35 PM seb_kuzminsky: so next what you probably want to do is bring your local 2.7 branch up to date with upstream/2.7, and same for master
01:35 PM seb_kuzminsky: so do this:
01:35 PM seb_kuzminsky: git checkout 2.7
01:35 PM seb_kuzminsky: git merge --ff-only upstream/2.7
01:36 PM Joe_Hildreth: it says my branch is up-to-date with upstream/2.7
01:36 PM seb_kuzminsky: ok good
01:36 PM Joe_Hildreth: I did not have to do the merge
01:36 PM seb_kuzminsky: then do the same with master (check it out, then merge upstream/master into it)
01:37 PM Joe_Hildreth: git log --graph --oneline --decorate master..upstream/master
01:38 PM Joe_Hildreth: belay my last, got this error: fatal: Not possible to fast-forward, aborting.
01:38 PM Joe_Hildreth: Mea Culpa
01:39 PM Joe_Hildreth: Thanks seb, I am in sync now and can push to my github and delete the issue branch I was using.
01:39 PM Joe_Hildreth: I will make some notes.
01:41 PM seb_kuzminsky: yeess, goood, let the power of git flow through you
01:41 PM Joe_Hildreth: HAHA, Thank you Jedi!
01:42 PM Joe_Hildreth: AM defiinately doing better than I was a few days ago. I you and cradek load of thanks.
01:42 PM Joe_Hildreth: I you/I owe you
01:51 PM Joe_Hildreth: One last question, are the docs in docs/src/gui ... authored in asciidoc? (I think that is what I remember someone saying.)
02:02 PM seb_kuzminsky: Joe_Hildreth: yeah, it's asciidoc
02:16 PM Joe_Hildreth: thanks
04:00 PM KGB-linuxcnc: 03Sebastian Kuzminsky 05master 0897246 06linuxcnc 10docs/src/code/code-notes.txt docs: fixup asciidoc markup in Code Notes * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0897246
04:38 PM KGB-linuxcnc: 03Sebastian Kuzminsky 05master f2d3a34 06linuxcnc 10docs/src/code/code-notes.txt docs: Motion mode doc updates for Joints/Axes * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f2d3a34
09:09 PM KGB-linuxcnc: 03Dewey Garrett 05master d30308d 06linuxcnc 10src/emc/usr_intf/axis/scripts/axis.py axis.py remove dead code, revise commentary * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d30308d
10:43 PM KGB-linuxcnc: 03Dewey Garrett 05master 9a1c381 06linuxcnc 10src/emc/usr_intf/axis/scripts/axis.py axis.py removed wrong func in preceding commit * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9a1c381
10:50 PM KGB-linuxcnc: 03Dewey Garrett 05dgarr/external_offsets 8802991 06linuxcnc 10(67 files in 13 dirs) External Axis Offset hal pins * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=8802991