GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.
WIP: Limiting occurrences of a new INFO message in MuonEfficiencyCorrections
The title says it all: this MR prevents e.g. log files from blowing up in size all of a sudden due to an new INFO message that is returned in some cases by MuonEfficiencyCorrections. Sorry I should have cached this before going forward with the previous MR.