Glad to see it shook loose.
Thanks for checking into it anyhow, Andy. I appreciate it!
-Greg
> On May 28, 2024, at 1:55 PM, andy pugh wrote:
>
> On Wed, 22 May 2024 at 12:29, Greg C wrote:
>
>> Looks like the git workflow is sticking on the package-arch “Test Debian
Looks like the git workflow is sticking on the package-arch “Test Debian
packages” step for Sid:
While it started falling on its face after my commit, I don’t believe my commit
to be the cause of the issue. Seems like a package is missing or broken. Just
wanted to bring it to …someone’s…
http://buildbot2.highlab.com/ is necessary for Bullseye and Bookworm.
Marius is talking about Buster.
The original buildbot is still building for Buster:
[image: image (1).png]
[image: image (2).png]
2.9.2:
[image: image (3).png]
Changing the Section(s) field to "master-rtpreempt" yields
My (perhaps unsolicited) opinion is that the person who merges the
PR/commits their own changes should carry it through to the upstream
branch(es). That way it's always tidy and there's no questions when the
next person goes to merge changes to code they're familiar with.
I generally try to do
Sebastian,
I made an issue on Monday that also speaks to this race condition that's
been exposed by the recent iocontrol moves.
Here is the issue: https://github.com/LinuxCNC/linuxcnc/issues/2700
I am not sure if Rene is on the dev list, so it might be prudent to make
these observations in the
Andy,
I think if Craftsman isn’t going to be updated to python3, then we should
consider removing it at least for this release. It can stay in master if
someone intends to do the work to update it.
Just my $0.02.
-Greg
On Mon, Oct 2, 2023 at 8:26 AM andy pugh wrote:
> I propose to freeze
gt;>> can sit here for a while.
> > >>> -John
> > vlc from a cli, stuttered and paused 90% of the time complaing mightily
> > about a lacking reference clock.
> > my connection seems to be sub par. or the site is busier than a one
> > armed paper hanger. :o)&
I think we’d all like to see them (and I don’t even know what “them”
entails).
Can they be uploaded to YouTube or something?
-Greg
On Wed, Apr 26, 2023 at 8:49 PM Stuart Stevenson wrote:
> I sent Jon copies. He can give them to anyone he wishes. I will give them
> to anyone that asks.
>
to have any
changes this step isn’t necessary).
gif stash pop
And your changes would be put back. I’m not sure what you changed.
If you may have added new files then you need “git stash -u” for the first
stanza.
On Sat, Apr 22, 2023 at 11:23 AM gene heskett wrote:
> On 4/22/23 09:35, Gre
Hey Gene,
I’m not a GitHub expert, but I the last time I had this issue the following
fixed it:
git rebase
I think the worst case is you delete the folder and re-clone and recompile
the project to a folder with the same name. Your configs and such should
be separate.
-Greg
On Sat, Apr 22,
Gene, et al,
After the buildbot does it’s thing (if you use package installs), this
should be fixed.
-Greg
On Sun, Feb 12, 2023 at 7:15 PM gene heskett wrote:
> On 2/12/23 11:49, Greg C wrote:
> > Good morning Gene,
> >
> > There is some discussion on this issue here:
>
Good morning Gene,
There is some discussion on this issue here:
https://github.com/LinuxCNC/linuxcnc/commit/56ecf76e11c5ce9feb78d3cd830c135db83c09d7#commitcomment-99885313
Thanks for the extra data points.
Looks like the fix for Bookworm and Sid inadvertently caused some noise for
those of us
What is the agenda of Daniel/Tormach's meeting?
-Greg
On Wed, Jan 18, 2023 at 7:33 PM Jon Elson wrote:
> Daniel Rogge of Tormach has mentioned that he is trying to
> set up a meeting in April with Robert Ellenberg, John Morris
> and Alex Rossler over a weekend. Does anybody have a
> specific
On Fri, Dec 23, 2022 at 6:39 AM wrote:
> I get the Message "Unknown g code used".
> How to debug this?
>
It may help to know what the gcode is...
>
>
> My beloved debug method "printf(...)" does not work.
>
use: fprintf(stderr, "your debug stuff here")
If it helps, after following the steps below, I can reproduce everything
described.
-Greg
On Sat, Dec 10, 2022 at 6:14 PM Dewey Garrett wrote:
>
> > Is anyone else able to reproduce this behaviour?
>
> $ wget www.panix.com/~dgarrett/stuff/arc.tgz
> $ tar xzf arc.tgz
> $ cd arc
>
> 1) start
Haha, thanks Andy. I'll save this for when others inevitably forget :-D
-Greg
On Sat, Dec 10, 2022 at 2:41 PM andy pugh wrote:
> On Sat, 10 Dec 2022 at 19:08, Greg C wrote:
>
> I wonder if anyone is opposed to adding a 0 and bumping it up 10x?
>
>
> Master is open
On Thu, Dec 8, 2022 at 10:39 PM Jon Elson wrote:
> On 12/8/22 20:12, Greg C wrote:
> > I wonder if anyone has insight to:
> > 1. Why MAX_POINTS was lowered?
> > 2. If I increased this back to 10 or even 100, are there any
> > potential negative side effects (I
Good evening all,
Recently on the forum turbostew brought up an issue that I've noticed in
the past (in PathPilot) where on large cut files, the backplot starts to
turn back to white at the beginning of the previewed cut paths. Thread
FWIW the preview works here on a Virtual Machine, homed in place with g2 as
the first move, G20 or G21.
12th Gen Intel(R) Core(TM) i7-12700KF
-Greg
On Wed, Dec 7, 2022 at 6:43 PM Peter C. Wallace wrote:
> On Wed, 7 Dec 2022, andy pugh wrote:
>
> > Date: Wed, 7 Dec 2022 21:54:41 +
> >
JT had said he was taking it down today around 5am central time to upgrade
from 30Gb to 50Gb storage since we were running at 90% used for quite some
time.
-Greg
On Thu, Jul 21, 2022 at 6:35 AM andy pugh wrote:
> I was on the forum earlier, but currently seem unable to connect.
>
> This is
>
>
> Does https://github.com/LinuxCNC/linuxcnc/pull/1764 fix this for you?
>
> Yes, it does. I took liberty to merge it. Thank you for noticing it was
out there.
-Greg
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
lock
lacks the 'Package' field
However if you try again with ./configure uspace, then it will work, but it
builds all docs.
-Greg
On Sat, Jun 11, 2022 at 4:41 PM Hans Unzner wrote:
>
>
> Am 04.06.22 um 12:41 schrieb Greg C:
> > Additionally, I would like to suggest that whet
I am confused on this as well. Unless I am reading this incorrectly, there
were builds that did complete (albeit with warnings) after that commit was
merged?
http://buildbot.linuxcnc.org/buildbot/grid
On Thu, Jun 9, 2022 at 8:11 AM Hans Unzner wrote:
> Am Do., 9. Juni 2022 um 11:25 Uhr
Hans, et al,
I don't mean for this email to take anything away from the 9 month effort
you and the team has put into making the docs more cohesive, as well as
translatable. Thank you to everyone on the team.
Unfortunately, the latest commit breaks a few things:
1. Building for anyone running
Thank you Andy for committing the docs changes.
Rainer - Perhaps one rainy cold Fall day I will start combing through them
to see if there is anything I can do to make it more clear. If nothing
else, I personally think it would be good to explicitly define the letters
for each G-Code.
Done.
https://github.com/LinuxCNC/linuxcnc/pull/1319
-Greg
On Mon, Oct 18, 2021 at 8:14 PM andy pugh wrote:
> On Mon, 18 Oct 2021 at 23:50, Greg C wrote:
>
> > Attached is my proposed changes to G74 and G84 in the docs.
>
> Is it possible to submit it as a pull r
Ok no worries, I will submit the pull request. I wasn’t sure which was
easier so I erred on this side.
Thanks Andy!
On Mon, Oct 18, 2021 at 8:14 PM andy pugh wrote:
> On Mon, 18 Oct 2021 at 23:50, Greg C wrote:
>
> > Attached is my proposed changes to G74 and G84
Rainer,
Attached is my proposed changes to G74 and G84 in the docs.
Please let me know if you think anything about it should be changed.
I did think of adding the R- and L- explanations to G81 too. But I am
trying to refrain from going too far down the docs editing rabbit hole.
Let me know if
Rainer,
Thank you for looking into it, very much appreciated!
Thanks,
Greg
On Mon, Oct 18, 2021 at 7:00 AM Rainer Stelzer
wrote:
> Hi Greg,
>
> > Although, I do wonder if no X or Y are given, should L still be valid?
>
> totally agree.
>
> I retrofitted some machines with Sinumerik 810
Good morning Rainer,
Thanks for the explanation, that makes sense.
Although, I do wonder if no X or Y are given, should L still be valid?
I will take a look at the docs later and see what I can do and submit a PR
to make it a bit more clear (at least for G74 and G84) for future “me’s”
:)
Good evening,
I spent some time today in the G-Code docs looking at G74 and G84 (left and
right hand tapping with a tension-compression head in mind) in an attempt
to fully understand the options.
I found the docs for these G-Codes to be a bit vague, and confusing.
Especially given that R- and
31 matches
Mail list logo
