Improve XML validation with custom XML entities#4783
Conversation
|
The stress test has been launched. The charts will be posted when they are ready. General
Stress test parameters:
Regards!. |
Analysis_dynamic_valgrind logcollector analysis:Commit: 32706c2a733134ab5e0437dd3a32cd95f13931db Lines executed:31.40% of 1860
Coverage report detail: coverage-report-summary |
Analysis_dynamic_valgrind syscheckd analysis:Commit: 32706c2a733134ab5e0437dd3a32cd95f13931db Lines executed:26.50% of 2996
Coverage report detail: coverage-report-summary |
32706c2 to
7c9da98
Compare
|
The stress test has been launched. The charts will be posted when they are ready. General
Stress test parameters:
Regards!. |
Analysis_dynamic_valgrind logcollector analysis:Commit: 7c9da98 Lines executed:31.40% of 1860
Coverage report detail: coverage-report-summary |
Analysis_dynamic_valgrind syscheckd analysis:Commit: 7c9da98 Lines executed:26.50% of 2996
Coverage report detail: coverage-report-summary |
|
The stress test has been launched. The charts will be posted when they are ready. General
Stress test parameters:
Regards!. |
Hello team, this closes #4767 .
We found that our XML validator was failing with directories such as:
This was due to the function that replaces XML entities before trying to validate the file, replacing every
\<for<, resulting in<<for the case above.The solution was to add the character
\as a new XML entity. In addition to that, I refactored the code to include more custom XML entities in the future (if needed) using a simple python dict.Before the fix
After the fix
Regards.