You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging an experiment, Python errors should appear in the console (i.e. NameError etc.)
Current Behavior
In Dallinger version 10.1.0a1, adding random text to experiment.py will correctly cause an error to appear in the console. Doing the same in models.py will result in a generic error stating an "internal server error" but will not specify where the error occured. This makes debugging very difficult.
Steps to Reproduce (for bugs)
Take a working experiment (e.g. Bartlett1932)
Add random text into models.py and attempt to run using dallinger debug --verbose
Context
I was trying to build a new experiment, but wasn't able to properly debug early code because the experiment would not launch.
Your Environment
Dallinger version used: 10.1.0a1
Operating System and version (desktop or mobile): Desktop Ubuntu (virtual machine) 22
Browser and version (e.g. Chrome 39, node.js 5.4): Chrome 124
The text was updated successfully, but these errors were encountered:
Expected Behavior
When debugging an experiment, Python errors should appear in the console (i.e. NameError etc.)
Current Behavior
In Dallinger version 10.1.0a1, adding random text to experiment.py will correctly cause an error to appear in the console. Doing the same in models.py will result in a generic error stating an "internal server error" but will not specify where the error occured. This makes debugging very difficult.
Steps to Reproduce (for bugs)
Context
I was trying to build a new experiment, but wasn't able to properly debug early code because the experiment would not launch.
Your Environment
The text was updated successfully, but these errors were encountered: