- Sep 06, 2022
-
-
richard.petersen authored
-
- Sep 02, 2022
-
-
richard.petersen authored
-
richard.petersen authored
This commit contains a fixup for the original commit 64f2780a
-
- Sep 01, 2022
-
-
richard.petersen authored
-
- Aug 17, 2022
-
-
richard.petersen authored
-
- 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
-