Config will not open after Buildbot2 upgade from 2.9.4 to 2.10
Is this error message generated by QTplasmac?
It is not documented anywhere I could see. In any case it should not continue to appear.
Attachments:
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
In this case the the config to upgrade was nothing more than a sim!
Issues:
- The m_files folder was in ~/linuxcnc/nc_files/examples/plasmac, copied it into ~/linuxcnc/nc_files
- The files in the m_files folder under examples were owned by root and the user did not have permissions to the M codes
- The INI M_CODE variable in the ini file was not updated in qtplasmac_metric_ini.inc. I suspect this was because its not the top level ini file (I'm not sure if you actually write to that folder)
- The error message should refer to plasmac so the user knows its specific to Plasmac. I had to deduce that by checking other configs
- The version number reported does not reconcile with the version details displayed on startup 2.10.0-pre-4165-xxxxxxxxxxxxxxxx
- Let me introduce you to Python try/except error handling www.w3schools.com/python/python_try_except.asp This would ensure the user is less bewildered when it fails. There is nothing displayed on the screen when it fails
- Perhaps the message could be a little more specific eg "updating qtplasmac mcode folder"
- Perhaps the upgrade message could also be printed on the console. Displaying Top right when console is in bottom left meant I did not even see the error the first couple of times!
Please Log in or Create an account to join the conversation.
Snowgoer
Greg … just in case you somehow missed it after all these years
Nope, i will continue with Snowwy !
Please Log in or Create an account to join the conversation.
Thanks Greg, I've beem away for years and find a bug in 5 minutes
You've been doing a lot of posting over the years for someone who has been away for years ...
I'd hold the back patting, I think you have something else going on ...
The m_files folder was in ~/linuxcnc/nc_files/examples/plasmac
Perfect that's where they're supposed to be:
github.com/LinuxCNC/linuxcnc/commit/d4bf...8829a665f015f1982562
Note that this ends up being nc_files/examples/plasmac/m_files on a package install.
The files in the m_files folder under examples were owned by root and the user did not have permissions to the M codes
That's possible, I don't do much with package installs, but it shouldn't impact the end user either way.
I installed the latest package on buildbot2 for bookworm a few minutes ago, it opened the qtplasmac_l_metric simulation without issue, no update messages, etc.
The INI M_CODE variable in the ini file was not updated in qtplasmac_metric_ini.inc. I suspect this was because its not the top level ini file (I'm not sure if you actually write to that folder)
This was fixed on Sept 6, 2024. Commit notes:
qtplasmac: fix m_code pathing
Fixes the m_code path for a package install sim.
Allows update 001-017 to be applied correctly for configs that were build prior to then.github.com/LinuxCNC/linuxcnc/commit/da67...c33db02daefaa2460e18
The error message should refer to plasmac so the user knows its specific to Plasmac. I had to deduce that by checking other configs
Did you think it referred to QtDragonHD, or Axis?
I suppose it could say something to the effect of "QtPlasmaC configuration changes mandated at V2.10-001.017 were applied". As a developer it's not always easy to know how the end user will interpret a message. Since January 23, 2024 you are the very first to complain.
The version number reported does not reconcile with the version details displayed on startup 2.10.0-pre-4165-xxxxxxxxxxxxxxxx
It's not supposed to. The main takeaway from the message is you have to restart QtPlasmaC. Similar to this case, the screenshot helps us with figuring out where the issue might lie.
Let me introduce you to Python try/except error handling www.w3schools.com/python/python_try_except.asp This would ensure the user is less bewildered when it fails. There is nothing displayed on the screen when it fails
I am quite aware of try/except error handling. It's pompous comments like these coupled with the shameless back patting that usually serve to make me sorry I tried to help you in the first place.
Both functions are wrapped in try/except, as interacting with the filesystem sometimes results in unexpected behavior.
There must be something going on with your OS/Installation. Simulations work fine on version V2.10-008.056 for a Package install and V2.10-008.061 for RIP. No update messages.
Perhaps the message could be a little more specific eg "updating qtplasmac mcode folder"
It serves the purpose as is.
Perhaps the upgrade message could also be printed on the console. Displaying Top right when console is in bottom left meant I did not even see the error the first couple of times!
Click the Statistics tab, there's a MACHINE LOG frame, it'll be there. machine_log_{date/time}.txt in the config folder also reflects the log on the Statistics tab. It's also in the "update_log.txt" file in the config folder.
I might add Joco is also in trouble over this for adding these gcodes!
Ok.
Please Log in or Create an account to join the conversation.
In particular, that update is looking for 'nc_files/plasmac/m_files' in your USER_M_PATH, to be able to see the Mxxx files. It’s not seeing it so it’s trying to update the ini file to fix it.
Perfect that's where they're supposed to be:
Your previously advised location was different. What is correct?
That would be expected. You would need to install on 2.94 then upgrade to 2.10 to replicate the issue. Confirmed behavoiur on 2 different PC'sI installed the latest package on buildbot2 for bookworm a few minutes ago, it opened the qtplasmac_l_metric simulation without issue, no update messages, etc.
This was not fixed for sims because I installed packages dated Feb 2025 from the buildbot. Bug remains.This was fixed on Sept 6, 2024. Commit notes:
Did you think it referred to QtDragonHD, or Axis?
I suppose it could say something to the effect of "QtPlasmaC configuration changes mandated at V2.10-001.017 were applied". As a developer it's not always easy to know how the end user will interpret a message. Since January 23, 2024 you are the very first to complain.
I had no idea as Axis, QTdragon and QTplasmac.sim configs were installed on my PC.
Clearer messaging would be nice
I had a specific reason to test upgrade from 2.9.4 to 2.10.
Sadly, the buildbot must be stuck again if it is that far behind for a package install done yesterday.There must be something going on with your OS/Installation. Simulations work fine on version V2.10-008.056 for a Package install and V2.10-008.061 for RIP. No update messages.
You would need to build for 2.9.4, install the sim, then open the config in 2.10 to replicate this error. Installing on 2.10 proves nothing as no upgrade will be triggered.
I can't use RIP given my customer is 1000 miles away and I want him to upgrade to 2.10 becasue you are no longer supporting 2.9
PC is running Trixie with kernel 6.12. But it also happened on a Bookworm PC. I think Debian version is irrelavent. (Trixie is only a couple of months away and 2.9.4 will be in it)
There is no erors in any of the MACHINE logs. There is no information in the update logs. We need better error reporting.Click the Statistics tab, there's a MACHINE LOG frame, it'll be there. machine_log_{date/time}.txt in the config folder also reflects the log on the Statistics tab. It's also in the "update_log.txt" file in the config folder.
Please Log in or Create an account to join the conversation.