evalution

getUserMedia is not available on WKWebView, which Capacitor uses. So you won't be able to use it unless Apple makes getUserMedia available in the future.

I think the issue is with the Lambda layer that was taking model.ouput. based on your eval_data and eval_target, I updated the model. So, please check the following model.

This is a problem with the name. The error message is clearly stating that 'Factor_2' is not valid. So you need to figure out what the actual column name is.

Use df.columns to get the column names.

Check for leading and trailing spaces. Is the comma part of the name?

Alternatively you could rename the columns.

You have a viewpager which should not be swipable?

Try making your custom viewpager like this:

In release mode, both versions of your code are identical.

In debug mode, there is a subtle difference as the lifetime of str will be extended until the end of the current method (for debugging purpose).

So this code in debug mode:

As mentioned in my comments earlier, please change

drop function with no parameter behave the same as drop with column name that doesn't exist in the Dataframe. You can follow the code in the source of spark.

Even in the function documentation you can see a hint to this behavior.

System Folder Properties: I think the answer can be found in this Symantec Article. Essentially: System Folder Properties are not affected by the ROOTDRIVE property.

Incidentally my D:\ drive has more space than my C:\ drive and ROOTDRIVE is set to D:\ in the MSI log file. Installation writes no files to D:\ though. I would think this is due to ample space on C:\?

UPDATE: Also check the documentation on TARGETDIR, with focus on this section:

"...if the TARGETDIR property is defined, the destination directory is resolved to the property's value. If the TARGETDIR property is undefined, the ROOTDRIVE property is used to resolve the path."

Problem Computer: The above does not really explain what happens on your problem computer, does it? Did you ever install manually to this custom location? Did you use a "Remember Property" pattern to persist the installation folder? It must be reading back that old path? Or maybe the disk is very low on space? Or are you installing using an admin image? AdminProperties. No Set Property custom actions in there? Could there be constructs in the GUI that could affect this? I know set property is used in some of WiX's default GUI sets. And you can make directories modifiable as "feature directories". See the screenshot down the page here.

Verbose Log: I would suggest you make a log file on a system where the installs go to a secondary drive and check what is written into the log with regards to ROOTDRIVE and directory resolution in general. In corporate environments where target computers are uniform many actually hard code ROOTDRIVE to C:\ - not great, but they do. They wouldn't do that unless they are trying to avoid some random side effect along the lines of what you describe.

Festivus Grievance: I have always disliked this ROOTDRIVE issue, and never fully understood it to be honest. I hear you in other words. It is in fact one of my Festivus grievances against MSI. Did I answer? Not really :-). You have some pointers at least. Maybe the WiX guys, Chris Painter or PhilDW can provide a complete answer.

Do Not Use the below construct:

Turns out it's a jasper studio issue. close/open Jasper Studio solved it.