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
SREPD has an errorMsg tea.Msg type for errors, and it's used in a number of places to return the errors, but for some reason the Update method does not handle these messages properly.
Examples include errors returned from the openOCMContainer() function:
debug 2023/12/11 09:44:51 [fork/exec /usr/bin/gnome-terminal: no such file or directory]
...as well as the acknowledge workflow, when ack'ing an already-resolved incident:
debug 2023/12/11 11:35:10 [setStatus HTTP response failed with status code 400, message: Invalid Input Provided (code: 2001): Incident Already Resolved]
debug 2023/12/11 11:35:10 HTTP response failed with status code 400, message: Invalid Input Provided (code: 2001): Incident Already Resolved
These messages are logged in the debug log, but not handled in the TUI.
The text was updated successfully, but these errors were encountered:
SREPD has an errorMsg tea.Msg type for errors, and it's used in a number of places to return the errors, but for some reason the Update method does not handle these messages properly.
Examples include errors returned from the openOCMContainer() function:
...as well as the acknowledge workflow, when ack'ing an already-resolved incident:
These messages are logged in the debug log, but not handled in the TUI.
The text was updated successfully, but these errors were encountered: