Hello, I'd like to be able to create a new group with some repos. Thanks for your work!
this was done
I have no idea what is Silence, but there are no deactivated accounts with that username neither groups in this gitlab server.
Please enable registration of Webauthn/FIDO2 security devices without TOTP.
To do this, simply enable the feature flag: webauthn_without_totp
.
Documentation: https://docs.gitlab.com/ee/user/profile/account/two_factor_authentication.html#set-up-a-webauthn-device
done
Historically the issue has been bots creating issues in other folks repos or snippets and not much a problem of new projects until last week.
My suggestion will be to shutdown completely 0xacab.org and not trying to solve this mess because in practice i've spent hundreds of hours cleaning the mess spam produces and nobody has done this work except a couple of days in several years.
I'm greatful for your help reporting this, it's actually just the second time we got this kind of help. But there is no need to try to find a solution. There is no bandwidth to keep this gitlab install going and there are enough alternatives around.
FAQ: [
{
Q: 'I have a support ticket!',
A: 'Please leave it at our issue tracker'
You need to sign in or sign up before continuing.
I'm scheduling time during the weekend to work on a few pending issues, I will make this one take a bigger priority... but it might be slow because I'm unfamiliar how the object storage software works.
Hi,
We use the default values for this setting, so it should work. I can check during the weekend this issue as I don't currently have one of these keys and I will need to find a token that supports it. I do have an idea where the problem comes from tho (particular to our setup), but i'm stuck until i find the hardware to test it.
more space was added, let's see how it goes from now
The artifacts killed our storage server as we weren't expecting so many big files. I'm unsure how we are going to handle the issue but this is a headsup as the ci jobs will fail because there is no space to upload the artifacts.
We have set up our own CI runner, but it can not upload the artifacts because they are too large (example job). The disk image is 4GB and there are some other files, so something like a 4.5GB limit should work for us.
According to the docs, this can be done in the admin area of GitLab.
The limit was increased to 6000MB from 300. I'm unsure how this will impact this service, but if there is a problem with this I will update this ticket. I consider this solved from now.