Changelog:
  - Injection of code to load stylesheets is now required to be resolved during
    the build process of ui projects.
    The plugin vite-plugin-ox-css is available.

Set cache control to no-store. The ui-middleware will then only look at the remote servers for the files and never in the local cache

Do not accept updates when the ui-containers are not available

this should help to get insights about how the caches are filled locally

richard.petersen authored 2 years ago and julian.baeume committed 2 years ago

Root cause: Due to a bunch of redis restarts, the bull-queues got unregistered and did not register again.
Solution: On every reconnect, readd the bull queue again.

Root cause: Express automatically redirected, fastify does not
Solution: Manually do the redirect

Root cause: mime types might contain charset information
Solution: be more relaxed about anything following the actual mime type

This commit contains a fixup for the original commit 64f2780a

richard.petersen authored 2 years ago and richard.petersen committed 2 years ago

Only warn, when meta.json is missing since the ui-middleware will fall back to a computed hash value

alexander.quast authored 2 years ago and richard.petersen committed 2 years ago

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

Cache lookups will immediately register a promise to prevent multiple requests for the same ressource

Use correct path for index.html for the memory lookup

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.

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