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.
Works around the issue in ATEAM-579 by injecting a new ForceIDConditionsAlg into the AthBeginSeq for the Run 3 DQ test script. Cleans up a few data dependency issues illustrated by running DQ with the MT scheduler.