08:11 alatiera: will be migrating the gst-htz-4 runner today, could use a register token
08:15 bentiss: alatiera: sent you one over PM
08:15 alatiera: bentiss thanks a bunch 🤗
13:27 Ford_Prefect: For an open MR, if a user did not have an email in an approved domain, then added it to their account, will the MR need to be reopened? (this is for tarun_ who just joined)
13:27 Ford_Prefect: to have the ability to run pipelines, I mean
13:31 tarun_: File "ci/gitlab/trigger_cerbero_pipeline.py", line 97, in <module>
13:31 tarun_: variables=variables,
13:31 tarun_: File "/usr/local/lib/python3.7/site-packages/gitlab/cli.py", line 71, in wrapped_f
13:31 tarun_: return f(*args, **kwargs)
13:31 tarun_: File "/usr/local/lib/python3.7/site-packages/gitlab/exceptions.py", line 338, in wrapped_f
13:31 tarun_: raise error(e.error_message, e.response_code, e.response_body) from e
13:31 tarun_: gitlab.exceptions.GitlabCreateError: 400: {'base': ['Insufficient permissions to create a new pipeline']}
13:31 tarun_: Cleaning up project directory and file based variables
13:31 tarun_: ERROR: Job failed: exit code 1
13:33 tarun_: ^ here is the error I am facing even I after an email with approved domain (Sorry for the plaintext, posting as snippet did not work somehow)
13:34 __tim: tarun_, Ford_Prefect, that's something specific to the gstreamer setup, basically that is not expected to work for people who don't have developer role in cerbero itself
13:35 __tim: The GStreamer merge bot will run it when the time comes, or you should be able to run a new pipeline Ford_Prefect, I think that'll work too
13:36 __tim: the script should probably catch that and print a proper error message
13:36 Ford_Prefect: ack, thanks __tim
14:43 karolherbst: oh now.. more spam
14:43 karolherbst: *no
14:43 karolherbst: I already sent a report
14:53 bentiss: karolherbst: please just add the Spam label instead to the issue, this blocks the user immediately
14:53 bentiss: except maybe not in nouveau
14:54 bentiss: karolherbst: we need someone to register drm/nouveau with damspam -> https://gitlab.freedesktop.org/freedesktop/damspam#usage-for-gitlab-project-maintainers
14:54 karolherbst: okay, will look into that later today
14:55 bentiss: we should probably register all of drm projects
18:00 karolherbst: bentiss: well.. I'm getting "gitlab.exceptions.GitlabAuthenticationError: 401: 401 Unauthorized"
18:18 eric_engestrom: karolherbst: did you include the scope `api` in your token?
18:18 karolherbst: I did
18:19 eric_engestrom: are you Maintainer or above on the repo you tried to add?
18:19 karolherbst: yes
18:20 eric_engestrom: did you replace `knockknock/whoisthere` with the actual repo? (I think we should replace that with a `replace_me` or something)
18:20 karolherbst: yes
18:21 eric_engestrom: no clue then 🤷
18:24 karolherbst: it kinda fails on the login it seems, so even before doing project stuff
18:26 karolherbst: uhhh
18:26 karolherbst: I created an access token on gitlab.com...
18:26 bentiss: karolherbst: have you told damspam to use your token?
18:26 karolherbst: because I clicked the link in the README :)
18:26 bentiss: oops
18:27 karolherbst: now I get AttributeError: module 'gitlab.const' has no attribute 'AccessLevel'
18:27 karolherbst: I guess I need to update my gitlab python stuff or something...
18:29 karolherbst: yeah.. that worked
18:30 bentiss: yep, I can see the issue created and then closed :)
18:30 bentiss: and that guy is now blocked
18:30 karolherbst: nice
18:31 bentiss: karolherbst: thanks :)
18:31 bentiss: karolherbst:and congrats, you are now part of the spam fighter task force ;)
18:32 karolherbst: .... I should have read the fine print first
18:32 bentiss: well, on drm/nouveau and mesa only I guess
18:32 bentiss: TBH, this spam fighting method has been *very* efficient
18:32 karolherbst: can I also use it on mesa or do I have to install it on mesa for myself as well?
18:33 bentiss: no, it's already setup for mesa, only one person has to do it
18:33 karolherbst: ahh, okay
18:33 bentiss: the idea is just that we want maintainers to opt-in in their project, and then anybody with developer role can set the spam label
18:34 karolherbst: so one assigns the label and the user gets nuked from everywhere?
18:34 bentiss: yep
18:34 karolherbst: nice
18:34 bentiss: the quickest we are the less likely the user opens another issue
18:34 bentiss: which means that everybody benefits
18:34 bentiss:goes afk