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.
This will make sure that we can use calo monitoring algorithms both with DetDesc and DD4hep. It fixes the way multi-threading issues and now accesses the detector element in the correct way.