[WINDOWS] On startup from the zip distrubtion main.R is not run

[gjwgit]

Description

For the zip distribution of the rattlng package for Windows, when running the rattle.exe on Windows, after R starts up in the CONSOLE it does not run the main.R script. On Linux and MacOS the main.R script is run on startup.

This task is to investigate why main.R is not run on starting up rattle.exe on Windows.

[gjwgit]

Note that I can paste the contents of main.R into the CONSOLE to have it run and then rattle will operate for that session as expected.

Perhaps it just needs main.R to be loaded later on - perhaps on the first (or every) loading of the dataset

[gjwgit]

Unfortunately this fix causes the following error for Linux:

flutter run --device-id linux
Launching lib/main.dart on Linux in debug mode...
Building Linux application...                                   
/home/gjw/git/github/gjwgit/rattleng/linux/flutter/ephemeral/.plugin_symlinks/flutter_pty/src/flutter_pty_unix.c:114:5: error: call to undeclared function 'waitpid'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
Error: Build process failed

Reverting for now.

[Lutra-Fs]

See TerminalStudio/flutter_pty#16. not test for linux so sorry for the issue introduced. I could create a fork with those fix and then we depend on that repo if you agree.

[gjwgit]

Let's give it a go.

[gjwgit]

Does this solve the issue for you @Lutra-Fs? I still do not have main.R being pushed into the Terminal on startup in Windows.

[gjwgit]

To investigate

• Copy and paste in the Console no longer functional?
• Move main.R into dataset_prep.R instead

[gjwgit]

I will stick with the main.R inside dataset_prep.R for now - there is a small delay after loading the dataset before the pages are populated but might be okay.

[Lutra-Fs]

Does this solve the issue for you @Lutra-Fs? I still do not have main.R being pushed into the Terminal on startup in Windows.

I didn't have that version in my pc so far. Will checkout the commit and see what happened here.

[Lutra-Fs]

Does this solve the issue for you @Lutra-Fs? I still do not have main.R being pushed into the Terminal on startup in Windows.

Just have a quick check and I could confirm that in my build main.R works fine even the loading is in start stage.

[Lutra-Fs]

[gjwgit]

We need to fix the version number problem on Windows so I can see the version in the screenshots - #273 - perhaps you could debug that. Thanks.

Can you share the screenshot of the Console tab - that is where the code is executed. It is simply displayed in the Script tab so there is no indication there that it has run.

On Linux and MacOS I see this:

[Lutra-Fs]

We need to fix the version number problem on Windows so I can see the version in the screenshots - #273 - perhaps you could debug that. Thanks.

Can you share the screenshot of the Console tab - that is where the code is executed. It is simply displayed in the Script tab so there is no indication there that it has run.

On Linux and MacOS I see this:

Just have a deeper test and you're right. The pty received the start.R first, then the R console is ready to go, so there should be some issue between flutter-pty ConPty and R

[gjwgit]

Thanks. Yes I suspect the async/sync needs work. In Linux I see the contents of main.R in the console before the R process starts, yet it gets executed anyhow. Same for MacOS I think. Seems like on Windows it does not end up getting executed or gets pushed to the Console before the console is ready. The process needs to be corrected to work under these scenarios.

[Lutra-Fs]

link to #298

[Lutra-Fs]

Looks like I got it fixed by adding extra measure to ensure Pty is correctly initialised then some extra delay.

[gjwgit]

This update did not seem to fix the problem for me on my Windows test machine. Plus running the test suite caused other tests to now fail. I have reverted the change.

[Lutra-Fs]

Sry for the delayed reply, the video is available at https://filesender.aarnet.edu.au/?s=download&token=d1a5d60a-cf57-41bc-b075-82b20b0f442b and will expire at 26/10/2024