Closed mkuratczyk closed 1 week ago
Sweet! It kind of sucks that we still do not have the new alpha builds infra for PRs but as soon as we sanity check it and merge, we will have a complete set of packages to try.
Not sure why Selenium suites begin to flake again but given the scope of the change, I assume that if some of them pass, then all of them should and these are, indeed, flakes.
The OAuth2 issue looks legitimate - seems to be a race condition based on whether prefs.js
is fetched before bootstrap.js is executed
Closing in favour of https://github.com/rabbitmq/rabbitmq-server/pull/12749/
What
Users should no longer run into issues with the Management UI when upgrading RabbitMQ. There are numerous reports of JavaScript errors, blank pages, or just header+footer pages (without the main content).
How?
index.html
refers to all our JS and CSS files with query stringv=$VERSION
and therefore the URL changes from version to versionmanagement_version
returned by the/api/overview
endpoint and compares it with its own version (defined in index.html). If there's a difference - a full page reload is performed (this is clearly an upgrade)Breaking change: we no longer support MSIE 8 :) (
evil.css
was a piece of history: https://github.com/rabbitmq/rabbitmq-server/commits/v4.0.x/deps/rabbitmq_management/priv/www/css/evil.css)