- Jul 19, 2023
-
-
david.bauer authored
-
- Jun 15, 2023
-
-
david.bauer authored
-
-
- Jun 09, 2023
-
-
david.bauer authored
-
- Apr 12, 2023
-
-
david.bauer authored
-
- Apr 11, 2023
-
-
-
david.bauer authored
- Unit and Integration tests now use "inject" instead of starting a server and using supertest. - Add Coverage Reports and "test:dev" mode. This enables a mocha --watch like workflow using nodemon, as --watch does not work with esm modules. - Reorganized and renamed files and functions
-
- Sep 02, 2022
-
-
richard.petersen authored
-
- Jul 11, 2022
-
-
Changelog: - Changed all 'trace' logs to level 'debug' - Added logging to the version check functions on log level 'info' and 'debug' - Added some time measures on ready checks to see what's taking so long on startup
-
- May 16, 2022
-
-
richard.petersen authored
Root cause: If multiple connections are opened at the same time after an update, the ui-middleware will do multiple requests to get initial data. That went especially worse, when e2e-tests are launched against ui-middlewares with multiple clients connecting at the same time. Soltion: Make sure, that a node already caches stuff without a response.
-
- May 09, 2022
-
-
richard.petersen authored
Root cause: configuration was only reloaded on those nodes, that did the version update. The other nodes might not notice that. Solution: On propagated version changes, the nodes always check for config changes
-
- May 04, 2022
-
-
richard.petersen authored
-
richard.petersen authored
-