jamovi

thanks zach,

yeah, it's defs something we should do. thanks for raising the issue again.

jonathon

for the record, manually typing in the data shouldn't make a difference, but its hard to say without seeing the data.

glad you've got it working

jonathon

Hi,

I wouldn't worry about jamovi-engine.exe ... that's not intended to be executed directly.

(Here's an LLM response)

Rather than guess at exclusions, the cleanest path is to let Defender tell you exactly what it's blocking and whitelist precisely those. Everything logs its own events:

1. ASR ...

assuming this is from the analyses that jamovi ships with (and not from a module).

i think there's something unusual about your data ... but jamovi is not providing a helpful error message here ... double check you're using a recent version of jamovi, as we do improve error reporting over time ...

try the 2.7.35 ... i think we've finally figured out this issue.

kind regards

jonathon

Thanks Jorge,

You're right, bug in the 2.7.32. I've rolled the web to 2.7.31, and sent a fixed 2.7.33 off to the build machinery. Expect 2.7.33 in the next hour or two.

Thanks for reaching out.

Jonathon

ask not what jamovi can do for you! but what you can do for jamovi!

Feel free to open a PR over here:

https://github.com/jamovi/jmv

cheers

Jonathon

fixed. thanks.

they're there on purpose ... the become readable when you hover over them ... if someone else complains, i'll change them. they seem OK to me.

jonathon

tell me more?