-
Notifications
You must be signed in to change notification settings - Fork 2
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
GUI dae: make more robust [Timebox 1.5 days] #8568
GUI dae: make more robust [Timebox 1.5 days] #8568
Comments
Just to be certain, and to confirm priorities, has this been seen on any other instruments yet? |
No - we did check other instruments and this behaviour was not seen. It is likely to be some peculiarity of OSIRIS' DAE setup which caused this. But this ticket I think should mostly be about generally hardening/logging more in this part of the UI, so that a similar problem is easier to debug next time, rather than trying to chase the exact stack trace. |
Possibly disable functionality as an interim solution, if not too involved. |
The PR addresses the exception that was coming. The complicated logic of highlighting unsaved changes has been left untouched. |
Issue Description
As a user on OSIRIS, I would like to be able to change my DAE parameters (e.g. timing source) through the IBEX gui.
For reasons which are unclear, attempting to change any parameter on NDXOSIRIS led to:
This is all to do with the (rather complex/hard-to-understand) mechanism we have for highlighting DAE changes which have not yet been applied.
This ticket is to try to make the DAE view as a whole more robust against this type of error (acknowledging that this exact error will be hard to reproduce):
LoggerUtils.logErrorWithStackTrace
is used when catching errors so we get a full stack traceReproducible (Yes/No)?
No
recovery.run
None of the above helped on OSIRIS.
Additional Information
Acceptance Criteria
This ticket is to try to make the DAE view as a whole more robust against this type of error (acknowledging that this exact error will be very hard to reproduce):
LoggerUtils.logErrorWithStackTrace
is used when catching errors so we get a full stack traceHow to Review
Before making a PR...
If not applicable, write "Not applicable"
To the reviewer: Make sure to update submodules!
Time in recording of planning meeting: 00h20m 2024/11/28
The text was updated successfully, but these errors were encountered: