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 in our documentation.
Admin message
Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
Since it isn't possible to change the number of udp- and background workers after the privileges have been dropped (except when knotd is being run under the root account, which is deprecated), there is no need to support dynamic reconfiguration of the number of workers. As the tcp-worker code will be moved to reuseport soon as well, the dynamic reconfiguration of the number of tcp-workers is removed too.
