[Bug]: R Code Calculation Not Executed After Clicking "Compute Column"

[EhudLevitin]

JASP Version

0.19.3

Commit ID

No response

JASP Module

Unrelated

What analysis are you seeing the problem on?

Edit Data

What OS are you seeing the problem on?

Windows 11

Bug Description

When creating a new variable using R code, clicking "Compute Column" does not always trigger the calculation. Sometimes the variable remains empty and the computation does not run.
Sometimes (mostly not), a spinning circle appears next to the variable name, as if the software is processing, but the calculation never completes and no result is displayed.

This issue does not occur consistently, but when it does happen, switching to Analyses mode and then back to Edit Data usually resolves it — the variable is then computed correctly and the values appear as expected.
This issue is most noticeable when using the ifElse() function, but it can also happen with simple arithmetic formulas.

I add a video of the bug :

Bug.Compute.Column.mp4

Expected Behaviour

The variable should be calculated immediately after clicking "Compute Column", and the results should appear in the data table without needing to switch modes or take any additional steps.

Steps to Reproduce

Create a new variable using R code :
ifElse(Height<=1.6,1, ifElse(Height<=1.7,2,3))
Click Compute Column

Log (if any)

No response

More Debug Information

No response

Final Checklist

• I have included a screenshot showcasing the issue, if possible.
• I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
• I have accurately described the bug, and steps to reproduce it.

[boutinb]

Hi @EhudLevitin Quite strange indeed. It would help if you can send us the log files when this happens again. I'll try to reproduce it.

[tomtomme]

@EhudLevitin
I tried your filter code with data from the library and it worked fine. So sending your data file may also help us

[EhudLevitin]

@boutinb
How can i get / find the log file ?

[EhudLevitin]

@tomtomme

Here is the file :
Bug_Lables.zip

Please note that mostly it works, but in class of 40 students, doing around 10 calculations each, it happens at least once .
I'm not sure if this is related, but it seems that under certain conditions, the issue becomes more frequent.
During class, there are alternating segments of practice and explanation, with breaks in between.
It appears that when there's a significant period of inactivity (about 15 minutes) without using JASP, the likelihood of the issue occurring in the next computation increases.

[boutinb]

It could be that an Engine after some time does not function anymore. Some people told us that, but this is quite hard to reproduce... To set up the log files, cf https://github.com/jasp-stats/jasp-desktop/blob/development/Docs/user-guide/logging-howto.md. If you set your machine with log on, so when it happens, hopefully we can see something in these logs.