[08:49:03] <kormat>	 is there a way to see what tags/subscribers were on a task when it was initially created?
[08:51:11] <elukey>	 the only way that I can think of is checking the history of changes in the task's timeline
[08:52:55] <jynus>	 phab notifications are also bugged, and subscribers when a task is created normally don't receive the task creation notification
[08:54:50] <kormat>	 grmbl
[08:54:54] <kormat>	 ok, thanks :)
[08:54:57] <moritzm>	 I don't believe the UI allows to directly show it, you'd need to comb through the history and deduct the tasks/subscribers which got added over time
[08:55:24] <moritzm>	 but it's probably possible via the Conduit API if you really need it
[08:55:40] <kormat>	 moritzm: i definitely don't need it _that_ much :)
[08:55:47] <moritzm>	 ok :-)
[10:34:45] <RhinosF1>	 kormat: which task? (If it's public)
[10:43:19] <kormat>	 RhinosF1: oh it wasn't very important; the task was https://phabricator.wikimedia.org/T286763
[10:44:11] <RhinosF1>	 kormat: looks like only me was added later
[11:44:45] <kormat>	 RhinosF1: ack
[11:58:15] <kormat>	 anyone know what the right sre team would be for handling an undeployed mw extension? https://phabricator.wikimedia.org/T235752#7398055
[12:13:43] <RhinosF1>	 kormat: a mix of releng and nice people who will do config patches for you
[13:36:36] <effie>	 kormat: I am not sure there is something to be done from an SRE perspective 
[15:35:34] <andrewbogott>	 boy, once I get 70 or 80 https warnings I start to think there might be an actual problem
[15:47:53] <Guest4714>	 DX? that is "the app formerly known as Watchmouse and 3 other things" and I _think_ the issue is related to the Letsencrypt root cert thing
[15:47:59] <Guest4714>	 oops, fixing nick
[15:48:42] <mutante>	 yea, "Peer certificate
[15:48:44] <mutante>	 cannot be authenticated with given CA certificates"
[15:48:53] <mutante>	 that sounds like it's all the same (known) thing
[15:53:41] <volans>	 mutante: yes, already discussed, O11y should be on it ;)
[15:56:22] <mutante>	 volans: ACK, thanks
[15:56:24] <mutante>	 andrewbogott: ^
[15:56:39] <andrewbogott>	 thx
[15:57:05] <andrewbogott>	 I figured it was known but due to a filtering fail all those emails were landing in my inbox :)
[18:05:15] <mutante>	 volans: fyi, on cumin1001: Service[rsync]/ensure: ensure changed 'stopped' to 'running' (corrective)  (does something else stop rsyncd and puppet then starts it again)
[18:06:56] <volans>	 mutante: rsync for what? it might be the new os reports moritzm added
[18:08:13] <mutante>	 volans: uhm.. just rsyncd itself as the service but no specific config snippet in /etc/rsync.d as I would expect. maybe WIP
[18:08:20] <mutante>	 looking some more
[18:10:17] <mutante>	 it's _trying_ to start it but it fails because /etc/rsyncd.conf does not exist
[18:10:33] <mutante>	 guessing there was some test and remnants from it
[18:27:38] <mutante>	 volans: yes, it's from osreports indeed. just leaving a message to him