-
Notifications
You must be signed in to change notification settings - Fork 181
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
Improve the error handler on the configuration save #4116
Conversation
message: errorMessage || error, | ||
title: `${error.name}: Mitre alerts could not be fetched`, | ||
message: errorMessage || error, | ||
title: "The configuration couldn't be saved.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: The file is saved, but it could be some validation errors. The message could be confusing.
…into fix/configuration-save-error
review <ossec_config>
<global>
<jsonout_output>yes</jsonout_output>
<alerts_log>yes</alerts_log>
<alerts_log2 realtime2="yes" >no</alerts_log2>
<!-- Other settings --> and the toast is displayed, but the error is a string, so the conditional block is not modifying the error message. This behavior could be changed due to the chages in the PR #4119. I merged the last changes and it seems to be working. |
|
Summary
Closes #4071
This PR improves the error handler when the configuration save fails.
This adds better messages that will ease the debugging if the error happens again.
To test
git apply force_save_error.txt
'This error has been forced. It is fine.'