Config will not open after Buildbot2 upgade from 2.9.4 to 2.10

There is no error.  It’s informational.  There’s over twenty logs of updating to 001.017 in the update log file.

As I said, expecting handling is present:

github.com/LinuxCNC/linuxcnc/blob/0e1f56...asmac/updater.py#L31

github.com/LinuxCNC/linuxcnc/blob/0e1f56...asmac/updater.py#L42

Nonetheless all of that is irrelevant; something’s up with your installation/OS.  All of the issues you mentioned have been taken care of for some time now. 
 

rodw wrote:

Yes, there are over 20 messages saying it upgraded but not one message saying it got an error and failed during that upgrade attempt.

That's because it didn't fail, at least not in the eyes of the try/except handler.

You can see I tried several times tying to get to the bottom of it, each generating a message.

The issue is that on two different PC's, the upgrade to a sim install failed without reporting an error which left me in the dark.

I don't know what you mean by "the upgrade to a sim install". Could you please elaborate?

You seem unwilling to actually test such an upgrade process and instead want to blame my installation.

I wouldn't say I am unwilling, even in the absence of steb-by-step directions from you as to how to reproduce what it is you are experiencing, I took my own steps to try to duplicate your issue:

I removed the package version I had installed, added the secret buildbot, and installed master for bookworm. I then launched linuxcnc by typing linuxcnc in the terminal. Navigated to Sample Configurations > sim > qtplasmac > qtplasmac_l_metric, and clicked OK. It worked fine with no update messages. I repeated for a RIP installation, it worked fine with no update messages.

The thing is that this issue has been solved by the aforementioned commits, and a sim config never needs to be updated, as it has the necessary changes. So it leads me to the conclusion that something went wrong in the process of going from 2.9.4 to 2.10.

Are you copying the config and trying to make a usable machine out of it? Or are you trying to actually simulate your machine?

If it's the latter, there's a way to simulate your actual table.

rodw wrote:

2. Install the Qtplasmac sim to the config folder
3. Open the sim to confirm its working

2. How? Why?
3. when you do this, LinuxCNC will copy the sim config folder to your "linuxcnc/configs" folder, so there is absolutely no reason for 2.
If you did 2. for whatever non existing reason, that might be the issue with permissions...

tommylight wrote:

rodw wrote:

2. Install the Qtplasmac sim to the config folder
3. Open the sim to confirm its working

2. How? Why?
3. when you do this, LinuxCNC will copy the sim config folder to your "linuxcnc/configs" folder, so there is absolutely no reason for 2.
If you did 2. for whatever non existing reason, that might be the issue with permissions...

I too am miffed by what you mean for #2.

Are you saying that you are trying to open the 2.9.4 sim config that was probably put in "My Sample Configurations" on a 2.10 installation?

If so, that could be the problem, just open a simulation from Sample Configurations > sim > qtplasmac > qtplasmac_l_metric.

(I think Tommy and I might be saying the same thing)

Here is opening a sample config on a fresh package 2.10 install:



Here is opening the copied config from my config folder, as well as from my sample configs on the launcher:

rodw wrote:

Just accept that I ran a Sim in Step 2 and it copied it to the configs folder
You tests prove nothing becasue you have not taken a sim installed under 2.94 then run it under to 2.10 (steps 5,6,7)
You are clearly not listening to the issue or following my instructions to replicate the issue. Tommy just goes off on a tangent on Item 2.

It seems neither Tommy nor I fully understood what you were doing in step 2. I follow now.

While waiting for clarification, I was attempting to replicate your issue and validate the process.

What I wanted to do is simply confirm using a SIM, things would work once I asked a customer to upgrade a live install on a production table over 1000 miles from me. Doing it on the sim found some issues. They may not apply to a live install.

Honestly, it seems like you’d benefit from learning how to simulate your customer’s actual machine. This guide explains how to convert a “live” config into a simulation config, which you may find more useful than the bog standard simulation config: forum.linuxcnc.org/plasmac/43425-simulator-for-qtplasmac

I am done with this issue as I received enough information to solve the problem manually from Snowgoer's initial post.

It’s good you were able to gather enough information to solve the problem manually.

The core issue stems from the interaction between the .ini file and the .inc file, resulting in ini.combined. The changes were correctly applied to that file, but the problem is that it’s overwritten every time LinuxCNC launches, so it applies the changes repeatedly.

I still maintain that this is an issue related to your setup/installation and/or an unintended use case. That said, I’m considering adding a check for “expanded” in the filename and display a warning if it looks like an older simulation config is being used. I’m also considering tweaking some of the messaging to clarify this process moving forward.

Thanks for being patient with me while I worked through this.