On 1/13/23 15:16, Chris Morley wrote:
the -d in this line:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o
camnumber=1 cam_align
is the debug switch - that is why qtvcp is noisy. You can remove it when all is
good.
I have no experience with linuxcnc over ssh so cannot
the -d in this line:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o
camnumber=1 cam_align
is the debug switch - that is why qtvcp is noisy. You can remove it when all is
good.
I have no experience with linuxcnc over ssh so cannot really help with those
problems.
I don't
Subject: Re: [Emc-developers] Broken master 06jan23
On 1/11/23 16:43, Chris Morley wrote:
looks like you are using a command like this:
EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align
try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID}
cam_align
Thats
need to use this in the ini.
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o
camnumber=1 cam_align
Chris
From: gene heskett
Sent: January 12, 2023 5:43 PM
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master
.
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} -o
camnumber=1 cam_align
Chris
From: gene heskett
Sent: January 12, 2023 5:43 PM
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master 06jan23
On 1/11/23 16:43, Chris Morley wrote
On 1/11/23 16:43, Chris Morley wrote:
looks like you are using a command like this:
EMBED_TAB_COMMAND = qtvcp -d -c cam_align -x {XID} cam_align
try changing it to:
EMBED_TAB_COMMAND = halcmd loadusr qtvcp -d -c cam_align -x {XID} cam_align
Thats better, at least lcnc runs, but prints this
-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master 06jan23
On 1/11/23 16:02, Chris Morley wrote:
> FileNotFoundError: [Errno 2] No such file or directory:
> '/usr/share/qtvcp/panels/-d/-d.ui'
>
> This is weird, it's picking up the -d as a panel name.
>
: Re: [Emc-developers] Broken master 06jan23
[QTvcp][CRITICAL] Aborted from Error Dialog
Qtvcp encountered an error. The following information may be useful
in troubleshooting:
LinuxCNC Version : 2.10.0-pre0-483-g47f4f07e2
Traceback (most recent call last):
File "/usr/bin/qtvcp&q
directory when I
get some food hidden. Half an hour maybe.
From: gene heskett
Sent: January 11, 2023 3:10 PM
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master 06jan23
[QTvcp][CRITICAL] Aborted from Error Dialog
Qtvcp encountered
@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master 06jan23
[QTvcp][CRITICAL] Aborted from Error Dialog
Qtvcp encountered an error. The following information may be useful
in troubleshooting:
LinuxCNC Version : 2.10.0-pre0-483-g47f4f07e2
Traceback (most recent call last):
File
vismach_scara.ui
gene@GO704:~/linuxcnc/configs$
It indeed is not there. What package might that stuff be in? This has a
different flavor, and I hope all this noise is useful.
Thanks Chris. take care & stay well.
Chris
From: gene heskett
Sent: January 7, 2023 11:27 PM
To: emc-develop
:
LOG.error('Qtvcp Error with camview - is python3-opencv installed?')
LIB_GOOD = False
DEFAULT_API = 0 # CV.CAP_ANY
Chris
From: gene heskett
Sent: January 7, 2023 11:27 PM
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] Broken master 06jan23
I believe a root cause of this breakage was the difficulty of merging
the docs from 2.9 to master.
The merge resulted in a bunch of awkward conflicts. As always, the
conflicts were caused by files being changed in the same place in both
branches. In this case, the conflicts came from a
On 1/8/23 11:38, Jeff Epler wrote:
On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
I disagree with having to use pull requests for devs. (if I understood that
right)
We already have problems getting pull request reviewed and aproved.
I will not change this without consensus.
Thank you Jeff.
Chris
From: Jeff Epler
Sent: January 9, 2023 3:06 AM
To: EMC developers
Subject: Re: [Emc-developers] Broken master 06jan23
Thank you all for the discussion.
I merged #2251, closed #2250, and in a moment I'll "unlock" the master
bra
Yes it is! uvcvideo! Thanks!
Alec
On Sunday, January 8, 2023 at 06:12:33 PM UTC, gene heskett
wrote:
On 1/8/23 01:42, Alec Ari via Emc-developers wrote:
> Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's
> like 90% of the way there, I have an installer and
Thank you all for the discussion.
I merged #2251, closed #2250, and in a moment I'll "unlock" the master
branch.
Take care,
Jeff
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
On 2023-01-08 10:38, Jeff Epler wrote:
[Chris requested that I explicitly respond to each part of his message.
I will do so even though I have little that is constructive to add]
Thank you, the discussion is important for everyone I think.
These things seem like radical responses to an
> Gesendet: Sonntag, 08. Januar 2023 um 03:34 Uhr
> Von: "Jeff Epler"
> An: "EMC developers"
> Betreff: Re: [Emc-developers] Broken master 06jan23
>
> Thanks for speaking up about the problem as soon as you realized it.
> I have temporarily l
wrong with asking the question again I suppose - maybe the project has
changed it's mind.
But I don't think so.
Chris
From: andy pugh
Sent: January 8, 2023 7:13 PM
To: EMC developers
Subject: Re: [Emc-developers] Broken master 06jan23
On Sun, 8 Jan 2023 at 04:10
On Sun, 8 Jan 2023 at 04:10, Chris Morley wrote:
>
> Why would we change to 'main' ?
Github have a problem with the word "master"
I think that they are misguided in this particular case, but at the
same time I think that "main" is a clearer name than "master". Though
perhaps "dev" would be
[Chris requested that I explicitly respond to each part of his message.
I will do so even though I have little that is constructive to add]
On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
> Why would we change to 'main' ?
> How does the name change fix merge problems?
> It does
On 1/8/23 01:42, Alec Ari via Emc-developers wrote:
Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's
like 90% of the way there, I have an installer and everything, just need to
test it on CNC hardware.. Are the cameras you guys use for camview fall under
UVC
On 2023-01-08 06:43, Jeff Epler wrote:
On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
AFAICT the code (I didn't look at the docs mind you) is fixed.
What is actually broken in master now?
What are we trying to fix? The history?
Content of changes in 2.9 were discarded, instead
On Sun, Jan 08, 2023 at 04:06:07AM +, Chris Morley wrote:
> AFAICT the code (I didn't look at the docs mind you) is fixed.
> What is actually broken in master now?
> What are we trying to fix? The history?
Content of changes in 2.9 were discarded, instead of being added to
master. This
Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's
like 90% of the way there, I have an installer and everything, just need to
test it on CNC hardware.. Are the cameras you guys use for camview fall under
UVC (USB_VIDEO_CLASS / uvcvideo) or something else? Trying to
strategies see my other maillist talk.
The jest of is - why merge released branches into master at all.
Thanks
Chris
From: Jeff Epler
Sent: January 8, 2023 2:34 AM
To: EMC developers
Subject: Re: [Emc-developers] Broken master 06jan23
Thanks for speaking up
Thanks for speaking up about the problem as soon as you realized it.
I have temporarily locked the "master" branch on github until this
problem is resolved.
I understand that the idea of force-pushing master to 1d836df^ before
the problem was discussed and dismissed (on IRC?). I did not see this
On 1/7/23 11:03, Dewey Garrett wrote:
Yesterday (06Jan2023), I made a bad commit that breaks
master branch updates from 2.9.
I've notified key developers with more git experience
and suggest that users of git checkouts for the *master*
branch defer updates until someone figures out how to
fix
29 matches
Mail list logo
