Fake Live Data crash for incorrect path

[DanielMurphy22]

https://github.com/mantidproject/mantid/issues/34954#issuecomment-1385697957

Found during Manual Testing so may not be affecting users.

Describe the bug When the path to the fileeventdatalistener.filename property is wrong, and you try to select the ADARA_FileReader instrument in Load LiveData, MantidWorkbench crashes and closes

To Reproduce Follow the live data testing section ADARA Fake Event and set the following lines in your Mantid.user.properties file.

fileeventdatalistener.filename=REF_L_32035_neutron_event.dat
fileeventdatalistener.chunks=300

If the file path is set incorrectly, such as just the filename or with "/home/username/Desktop/Data/REF_L_32035_neutron_event.dat" (rather than the correct "/Users/username/Desktop/Data/REF_L_32035_neutron_event.dat")... When you try to Load > Live Data MantidWorkbench will crash and close Expected behavior It does not crash and offers a useful error message.

Platform/Version (please complete the following information):

• OS: macOS Monterey
• Mantid Version 6.6 manual testing nightly 15th Jan

[jhaigh0]

When I run the LoadLiveData algorithm I don't see ADARA_FileReader in the instrument list.

Do I need to change to a different facility?

[DanielMurphy22]

Change your facility to TEST_LIVE. Sorry the instructions aren't great, it mentions this in the manual testing instructions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[jhaigh0]

Still should be solved

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[github-actions[bot]]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.