Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"
Describe changes:
Previously, if the settings file was missing, or had typos that caused loading to crash the GUI would raise an exception, but in doing so caused a separate exception to be raised. This resulted in error messages that were uninformative.
Now, the exception is raised properly, more clearly indicating the problem.
Uncaught exceptions are now displayed with more white space for improved readability
What issues or discussions does this update address?
resolves #426
Describe the expected change in behavior from the perspective of the experimenter
Error messages should be more readable
Describe any manual update steps for task computers
Pull Request instructions:
Describe changes:
What issues or discussions does this update address?
Describe the expected change in behavior from the perspective of the experimenter
Describe any manual update steps for task computers
Was this update tested in 446/447?