This is an archived project. Repository and other project resources are read-only.

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.

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.

Config spamming on flows

For some reason, some clients are sent the configuration over and over again, seemingly eating a lot of bandwidth and CPU. Why is that?

flow@flow_plugin:257    2016-08-29 09:53:34,332 DEBUG   Sending config to 00000005000021a7
flow@flow_plugin:257    2016-08-29 09:53:34,338 DEBUG   Sending config to 000000090000177e

Edited Nov 12, 2020 by Vojtech Myslivec

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information