daniels changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
co1umbarius has joined #freedesktop
columbarius has quit [Ping timeout: 480 seconds]
Kayden has joined #freedesktop
utsweetyfish has quit [Remote host closed the connection]
utsweetyfish has joined #freedesktop
PuercoPop has joined #freedesktop
PuercoPop has quit [Ping timeout: 480 seconds]
ximion has quit [Quit: Detached from the Matrix]
Lyude has quit [Ping timeout: 480 seconds]
Lyude has joined #freedesktop
swatish2 has joined #freedesktop
i-garrison has quit []
i-garrison has joined #freedesktop
bmodem has joined #freedesktop
bmodem has quit [Ping timeout: 480 seconds]
bmodem has joined #freedesktop
bmodem has quit [Excess Flood]
tzimmermann has joined #freedesktop
bmodem has joined #freedesktop
psukys has joined #freedesktop
AbleBacon has quit [Read error: Connection reset by peer]
AbleBacon has joined #freedesktop
<slomo>
is there a way how i can mark a specific comment to an MR/issue as spam, and not the whole thing?
sima has joined #freedesktop
<MrCooper>
slomo: I think you need to use the abuse button on the user page
<MrCooper>
oh, there's also "Report abuse" in the comment's 3-dot menu
<slomo>
ok, but nothing like the spam label that then gets all handled immediately by a bot?
<MrCooper>
seems tricky to handle individual comments with that though
<bentiss>
MrCooper: indeed, but as long as it's not me who writes that code... :)
<DavidHeidelberg[m]>
mupuf: so only second patch is needed for 6.5?
<mupuf>
DavidHeidelberg[m]: sure
<DavidHeidelberg[m]>
send it upstream, in worst case some get not that perfectly functional device, but still better than nothing :)
<mupuf>
yeah, I agree
<DavidHeidelberg[m]>
anyway, at least I'll test 6.5 before merging the external kernel
Ahuj has joined #freedesktop
AbleBacon has quit [Remote host closed the connection]
<mupuf>
DavidHeidelberg[m]: I really don't get why you are trying to use the same kernel for valve infra. What's the point?
<mupuf>
and I still don't get how you plan on using your series... Would you set the variable as a pipeline variable?
<DavidHeidelberg[m]>
mupuf: you test new kernel against every device we have? Regressions?
<mupuf>
ok, so your goal here is to use mesa CI for pre-merge testing the kernel?
<DavidHeidelberg[m]>
you can test drm-next or whatever you need and be sure for example you didn't break other devices with your patches
<DavidHeidelberg[m]>
yup, we already have drm-ci which test drm stuff, but we still cannot verify the kernel will not regress in Mesa
<mupuf>
ok, so then you compile all the kernels, push them to S3, then mesa knows how to construct urls to download the resources
<DavidHeidelberg[m]>
well, you just push tag :P the kernels get compiled automagically :P
<mupuf>
ok, so that would be another "auto-uprev" process? Or do you really want to test the kernel in pre-merge?
<DavidHeidelberg[m]>
not in pre-merge (could be in future, but not yet). But yes, you push into gfx-ci/linux or your fork, you test with pipeline.. and then you can uprev MesaCI to that tag, when no problems shows
<DavidHeidelberg[m]>
so far I find it very useful to bump to new kernel, because very often something doesn't work right on first try, so generating new images is non-sense, until we know it's the final setup
<slomo>
bentiss: yeah i was wondering if that custom bot handles that somehow :) will just delete that one comment, might've actually also just been someone accidentally copy&pasting garbage from elsewhere into the comment field...
psukys has quit [Ping timeout: 480 seconds]
bochecha has joined #freedesktop
<bochecha>
hi all, hope everyone is ok :)
<bochecha>
I'm trying to setup damspam on my projects, and having a few difficulties :-/
<bochecha>
however, when I try to request-webhook, it says "One of --token-file or --token-env is required"
<bochecha>
ok, so I tried the same command with --token-file, and now I get "Error: No such option: --token-file"
<bochecha>
so, how to actually request the webhook? I'm not getting any spam yet, but I'd like to do my part and avoid them ince spammers find my projects ^^
<mupuf>
DavidHeidelberg[m]: ack
<bentiss>
bochecha: IIRC the --token-file parameter should be set *before* `request-webhook`
<bentiss>
bochecha: also make sure to have a token for gitlab.fd.o, not gitlab.com (as the readme points at the doc on gitlab.com)
thaller has quit [Ping timeout: 480 seconds]
rbanffy has joined #freedesktop
pkira has joined #freedesktop
a-l-e has joined #freedesktop
An0num0us has quit [Ping timeout: 480 seconds]
<bochecha>
that indeed solves this problem, although it's not at all obvious the order matters :(
<bochecha>
now it can't find the project after I give its full URL, I tried to give <namespace>/<project> and it says the object has no attribute 'is_admin'...
<bochecha>
(also, --help doesn't say anything at all about any parameters except for --help :( )
<pkira>
Hey, recently I've created some automation script that closes non-reproducing issues for Intel Xe and i915 projects. Issue is that GitLab treats comments (which have same content that explain why issue was closed) as spam. Do you know if it's possible to add some exceptions, per account maybe?
mripard_ has joined #freedesktop
mripard has quit [Read error: Connection reset by peer]
mripard has joined #freedesktop
mripard_ has quit [Ping timeout: 480 seconds]
ximion has joined #freedesktop
a-l-e has quit [Ping timeout: 480 seconds]
<bentiss>
bochecha: oh, that's a bug that was fixed on the main branch IIRC