20:00:00 <nitzmahone> #startmeeting Ansible Windows Working Group
20:00:00 <zodbot> Meeting started Tue Mar 22 20:00:00 2022 UTC.
20:00:00 <zodbot> This meeting is logged and archived in a public location.
20:00:00 <zodbot> The chair is nitzmahone. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
20:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:00 <zodbot> The meeting name has been set to 'ansible_windows_working_group'
20:00:03 <nitzmahone> bam
20:00:03 <briantist> sup
20:00:10 * jborean93 knew better to not even try
20:00:13 <nitzmahone> #info agenga https://github.com/ansible/community/issues/644
20:00:21 * nitzmahone learns to type "agenda"
20:00:45 <nitzmahone> nothing new, so
20:00:48 <nitzmahone> #topic open floor
20:00:50 <jborean93> anything on the Uganda :)
20:00:53 <nitzmahone> #chair jborean93
20:00:53 <zodbot> Current chairs: jborean93 nitzmahone
20:00:55 <briantist> haha
20:01:16 <briantist> GitHub has an open beta for ignore revs:
20:01:16 <briantist> https://github.com/github/feedback/discussions/5033
20:01:36 <nitzmahone> OOOH
20:01:45 <nitzmahone> yasssss
20:01:53 <briantist> I know we made a mass formatting change before and I had mentioned this file, even though it had to be used intentonally on the client side
20:01:58 <bcoca> nitzmahone: fyi, the 'file tree' i told you about is also beta feature
20:02:03 <jborean93> ah bummer I never actually added the ignore
20:02:09 <jborean93> should get onto that soon
20:02:12 <briantist> we still can!
20:02:15 <nitzmahone> we can add the ignore anytime
20:02:25 <nitzmahone> it doesn't have to be in the same commit
20:02:25 <briantist> bcoca: yeah I really like the filetree!
20:02:43 <bcoca> its useful for my prs since i modify 1293087234 files
20:02:48 <briantist> yup exactly, it helps if all the changes we want to ignore are int he same commit, but the file can be creates any time
20:02:56 <nitzmahone> Yeah, I still haven't actually *used* the filetree- I'm just so used to ignoring that whole side of the screen during code reviews :D
20:03:32 <briantist> heh yeah bcoca but those are meaningful changes.. unless you just want it to look like someone else made them ;)
20:03:41 <nitzmahone> It also means there can't be any logic changes in the commits we ignore though- only formatting
20:04:04 <briantist> for me the filetree is less about clicking and more about seeing where the file I'm looking at is, in context, it can be helpful
20:04:50 <nitzmahone> I have to remove my mental blinders and remember to look at it first
20:04:51 <briantist> anyway, they are openly accepting orgs to go into the beta, but it's not live otherwise, so if we wanna do that we need to ask them to enable it for `ansible-collections`
20:05:02 <nitzmahone> We'll get that going
20:05:05 <briantist> sweet!
20:06:18 <nitzmahone> oh, 3hrs ago `We have been working to get this shipped and it's available to anyone now!` - does that mean it's no longer a private beta?
20:06:49 <briantist> oh! maybe, thentofications on that issue since it was in beta were kinda of crazy so I havent'looked at every message since
20:07:07 <nitzmahone> Yeah, looks like they just lit it up for everyone a few hours ago
20:07:11 <briantist> speaking of good news out of GH, single job re-run and re-run failed jobs are finally live too
20:07:25 <jborean93> oh that's awesome
20:07:26 <nitzmahone> Yeah, I've used the latter a couple times already
20:07:33 <jborean93> one of the last remaining things I wanted to see with GHA
20:08:00 <nitzmahone> Interestingly, it works for AZP as well via the GH checks UI
20:08:08 <nitzmahone> (can't remember if that's new or not)
20:08:33 <briantist> still crickets on the bug I raised over a month ago though that is killing any motivation I have to work on docs build stuff: https://github.community/t/called-workflows-cannot-be-queued-onto-self-hosted-runners-across-organisations-enterprises-failed-to-queue-this-job-labels-ubuntu-latest/229355?u=briantist
20:08:56 <briantist> even with g-undalow emailing them... no progress 😢
20:09:42 <nitzmahone> bummer, haven't run into one of those yet
20:10:20 <nitzmahone> (but I'm also usually using self-contained workflows)
20:10:38 <briantist> it is kind of a niche bug, but really annoying..
20:11:14 <briantist> also no news of the strange issues with their windows 2022 runners: https://github.com/actions/virtual-environments/issues/5151
20:11:47 <briantist> at least they updated to say they didn't get a chance to look yet
20:12:18 <jborean93> I wonder if that's due to the weird VirtIO driver bug I came across with 2022
20:12:21 <nitzmahone> I assume that's WSL1, since IIRC WSL2 is not really supported on GHA runners?
20:12:28 <briantist> yup, WSL1
20:12:45 <briantist> jborean93: ooo what VirtIO driver bug? got a link?
20:12:54 <nitzmahone> oof, I assume it's BSODing or something
20:13:15 <briantist> it's so bad that the GH UI doesn't know how to handle it
20:13:31 <briantist> I have jobs cancelled/killed months ago that still show up as though they're sort of in progress
20:13:31 <jborean93> If it's bringing down the network connection it would explain no logs to some extent https://github.com/virtio-win/kvm-guest-drivers-windows/issues/583
20:13:38 <jborean93> But I would be surprised if it is that
20:15:35 <briantist> interesting, maybe the offload workaround will help in this case
20:16:26 <jborean93> IIRC it was only affecting DNS but it's been a while since I last looked at the problem. Worth a stab but I would be surprised if it's the issue there
20:17:18 <briantist> that kind of setting has been known to mitigate other issues on GH runners: https://github.com/actions/virtual-environments/issues/1187
20:18:00 <nitzmahone> WSL1 is some serious kernel-level magic, and they're clearly not testing it like they used to now that WSL2 is the Way Of The Future, so wouldn't surprise me if there are nasty bugs in new versions :(
20:18:32 <jborean93> Heh so maybe it will help, worth a shot :)
20:20:01 <jborean93> I've got nothing special to add, slowly slugging my way through adding tests for pypsrp. I believe I'm mostly done with the runspace/pipeline API itself, just need to try and remove a lot of the duplicated code and really test out the WSMan side
20:20:58 <briantist> sounds great!
20:26:09 <briantist> I got nothing else either
20:26:23 <nitzmahone> OK cool, guess we'll wrap it up for today then- thanks all!
20:26:27 <nitzmahone> Til next week!
20:26:29 <nitzmahone> #endmeeting