José Luis López Sánchez

> Once finished, we observed with @cborla and @nico-stefani that it had not been executed with the cluster performance test parameters. @nbertoldo, @cborla Luckily, it is possible to run the...

## Build 521 (v4.7.4) Artifacts: [artifacts_v474.zip](https://github.com/wazuh/wazuh/files/15296891/artifacts_v474.zip) | **Test** | **Status** | **Report** | |--|--|--| | test_cluster_performance | :red_circle: | [Report](https://github.com/wazuh/wazuh/files/15296903/test_cluster_performance.zip) |  As can be seen above, the test failed...

Good analysis @GGP1. An additional 25% time is relatively worrying, although we have no other option to get rid of werkzeug CVEs, we need to upgrade connexion. I wonder, however,...

> The connexion 3.0 performance degradation lays mainly in the new WazuhAccessLoggerMiddleware that logs every request to the api.log file. This part is key. Maybe we should consider using uvicorn's...

The failed checks are unrelated to these changes: ``` 2024/05/09 14:18:16 wazuh-modulesd:vulnerability-scanner: ERROR: VulnerabilityScannerFacade::initEventDispatcher: [json.exception.type_error.302] type must be string, but is object ```

Blocked until the development below is merged, as some dependencies are upgraded in it: - https://github.com/wazuh/wazuh/issues/20748

Blocked until the development below is merged, as some dependencies are upgraded in it: - https://github.com/wazuh/wazuh/issues/20748

ETA postponed to `12/09/2023`, reasons: - One week for the review of the [PR to the qa-framework](https://github.com/wazuh/qa-integration-framework/pull/25) and application of changes. - One week for the review of the [PR...

The failing framework unit test check is related to Jenkins. The same happened in v4.7.4.

I've run the coverage using the `v4.8.0-rc2` [requirements](https://github.com/wazuh/wazuh/blob/v4.8.0-rc2/framework/requirements-dev.txt) and I got a 92% :thinking: Something similar happened to @javiersanchz in the previous stage, it seems a problem related to the...