[05:45:22] <hashar>	 hi I am wondering whether something might have changed on the WMCS network side yesterday around 22:30 UTC,  we see npm taking twice longer than it used to and I wonder whether something might be throttling it on the network side
[05:46:16] <hashar>	 it is quite unlikely but I am asking just in case ;)   There are graphs of some npm based builds at https://phabricator.wikimedia.org/T437008#12288297 which shows they are twice slower (with a great certainity due to npm ci taking a lot longer)
[06:26:58] <godog>	 greetings
[06:27:02] <godog>	 not afaik hashar 
[08:02:58] <hashar>	 godog: thank you!
[08:03:17] <hashar>	 I wanted to rule out a potential change on the WMCS networking side (like throttling)
[08:19:41] <dhinus>	 morning
[08:21:55] <dhinus>	 hashar: fwiw I'm currently seeing very slow npm runs on my laptop, but https://status.npmjs.org/ says everything is fine...
[08:22:17] <hashar>	 ah great
[08:22:26] <hashar>	 so that might be an issue somewhere at upstream
[08:23:52] <hashar>	 I should try on fast speed connection with debugging on ;)
[08:34:49] <dhinus>	 hashar: I think it's this https://github.com/orgs/community/discussions/187552#discussioncomment-18280231
[08:35:02] <dhinus>	 adding --no-audit makes it fast on my laptop
[08:35:07] <hashar>	 ohhh
[08:35:24] <hashar>	 would you mind pasting it on the task at https://phabricator.wikimedia.org/T437008   (since you found it)
[08:35:31] <dhinus>	 sure
[08:35:34] <hashar>	 we did some change to audit / fund a couple days ago
[08:35:36] <hashar>	 thanks!!
[08:37:31] <dhinus>	 done
[08:38:07] <dhinus>	 <3 for the person who commented upstream with "Incredible how I need to visit a dead GitHub discussion instead of the Status page to find out if services are down or not."
[09:03:53] <hashar>	 dhinus: sounds like some persons like to be very mean on the internet :)
[09:04:11] <hashar>	 I am happy you found that link, cause I did some search earlier today and could not find anything
[09:05:05] <dhinus>	 I was lucky, I tried to find any kind of upstream bug tracker, found that one and it was one of the most recent discussions :)
[16:16:21] <bliviero>	  calling attention to https://phabricator.wikimedia.org/T437069.  is this something on our end?
[16:23:06] <andrewbogott>	 That probably is an SRE thing but probably is not much to do with tools-infra
[16:23:16] <dhinus>	 this is the production docker registry, not sure who the owner is
[16:23:27] <dhinus>	 maybe the new ownership spreadsheet will tell us? :P
[16:23:42] <dhinus>	 I mean the service catalog
[16:24:12] <dhinus>	 ah this is actually a single image that is broken
[16:27:18] <bliviero>	 thanks.   
[16:27:57] <bliviero>	 following a dialog on slack, this seems to have something to do with Bullseye LTS; thanks for confirming no action on our part
[16:29:51] <dhinus>	 maybe worth adding the generic "SRE" tag to the phab task?
[16:33:37] <bliviero>	 will do! thx for the suggestion