[12:55:14] !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed b270cde644 (very rudimentary lexeme support) [12:55:16] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [13:15:45] !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed 1b4ccaff9c (focus guess input on key press) [13:15:47] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [14:10:09] !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed 2db51d07e9 (support for most time values) [14:10:11] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [14:36:55] !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed 3ad25bd9e0 (support globe coordinates – all value types now supported 🎉) [14:36:57] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [15:27:10] !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed 894d8b3ef5 (three minor improvements) [15:27:12] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL [16:07:13] Trying a new debian image and it has the symlink resolv.conf -> /run/systemd/resolve/resolv.conf [16:07:23] I have never seen that before, has that somehow always been the case and I missed it? [16:08:31] I think it depends on which resolver you’ve installed, systemd-resolved might not have been the default before [16:10:10] that doesn't seem to be installed on either my before or after example [16:10:49] I am on Debian 13 and my /etc/resolv.conf is not a symlink to /run/systemd/ so far. But I hear on Ubuntu it is. [16:13:12] in my case I'm comparing a debian 12 daily build from today vs one from a couple of months ago. [16:13:21] Seems like a radical change to make within the same release version [16:13:40] But maybe it comes stock as a symlink and I'm used to hosts rearranged by puppet or something? [16:13:54] (I should note that in this particular case it is symlinked to a file that /does not exist/) [16:14:16] I think I will start by just trying a different daily [16:16:57] that does sound weird .. installing that package would replace the resolv.conf with that symlink.. but if it's not installed.. that sounds like a bug [16:17:29] a different daily sounds like a good idea. meanwhile asked in #debian [16:17:47] yeah, I will if I find the same thing in last month's build [16:18:20] https://packages.debian.org/search?searchon=contents&keywords=systemd-resolved&mode=path&suite=stable&arch=any [16:20:56] thanks, will keep an eye out for that [19:46:50] It appears to me for any patch: Forbidden [19:46:51] You don't have permission to access this resource. [19:47:09] (like: https://gerrit.wikimedia.org/r/c/1150027) [20:31:11] GergesShamon, sorry for the cliche, but can you try logging out of gerrit and back in? [21:35:00] @GergesShamon: It is possible that your traffic is coming from an IP block that has been blocked because of some unwanted web crawler traffic. Does the web page you see look like a Gerrit response or does it look more like a Wikimedia error screen? [21:38:20] If there is a "contact noc@wikimedia.org" message at the bottom of the page, you should do that and provide your IP addresses. Both IPv4 and IPv6 if you are dual stack enabled. [22:07:22] The problem is with the browser. (re @wmtelegram_bot: @GergesShamon: It is possible that your traffic is coming from an IP block that has been blocked because of some unwante...) [22:11:17] If they were throttled on our side they should either see a 429 error or it would just time out and not load at all. But the part that they say explictly "Forbidden" makes me think it isn't us. [22:13:54] ah, it could be on apache level though if it matches a user agent string considered a "bad_browser" [22:15:09] GergesShamon: is it any of these: Chrome older than version 125, Firefox older than version 100, Windows 7 or older [22:15:29] works in newer browsers? [22:16:23] also: Mac OS X 10.6 and older