Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Inline_Script into opensesame results in "non responsiveness" #810

Open
CelineHonekamp opened this issue Feb 2, 2024 · 3 comments

Comments

@CelineHonekamp
Copy link

Hello,
I have not yet written an issue, so excuse me if I do forget important information or do not follow any regulations or guidelines on doing so!

I just downloaded/installed OpenSesame from conda/pip (followed the instructions on the webpage closely) and am struggling with openSesame. The moment I drag the python inline_script component into my project, the whole thing "crashes"

Below you can see the repeated warning I get on my conda prompt:
[2024-02-02 10:47:45,108:subprocess_manager:60:WARNING] main process is alive but unresponsive
SHGetFileInfo() timed out for Run2.py
SHGetFileInfo() timed out for Prepare1.py

What do I need to do to fix this?

@smathot
Copy link
Collaborator

smathot commented Feb 5, 2024

Hi @CelineHonekamp , Could you provide more information? Specifically, what happens exactly when "the whole thing crashes"? What operating system do you use? And how did you install OpenSesame exactly (conda can be quite finicky, so the exact details matter)?

@CelineHonekamp
Copy link
Author

@smathot Hi!

"the whole thing crashes": it just gets unresponsive - it stops doing anything
operating system: Windows 11
installation: I used conda and the exact commands adviced in the installation guide, I was then missing some toolkit called "tomlkit" or something which I installed myself then! - should I re-install it using the normal installer?

@smathot
Copy link
Collaborator

smathot commented Feb 5, 2024

Hi @CelineHonekamp , I suspect that this is something specific to your installation. (Although I have no idea what.) So yes, can you try the regular installer? If this is works fine, please report back and then I'll close this issue. If you experience the same issue with the regular installer then we'll take a close look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants