Jeff Lill
Jeff Lill
We should have our cluster operator handle thing like this. I think I added a related issue for namespaces a week or two ago. The rational is that setup is...
**CLOSING:** **pubcore** is much faster, now that we're publishing to directly a project external folder so this really isn't that big of an issue any more.
I'm reopening this because it'll probably be a worthwhile productivity enhancement.
After reading the whole thread for microsoft/WSL#5324, it looks like MSFT has identified this as a Linux kernel bug and has a fix in the works. Looks like it'll be...
Microsoft claims to have fixed microsoft/WSL#5324 but people are still having trouble (as are we). It looks like this is going to be fixed in a new kernel release? Here...
One quick workaround for unit testing might be for have the Docker related fixtures run this before starting anything: ``` sudo hwclock --hctosys ``` Here's the manual for this: https://man7.org/linux/man-pages/man8/hwclock.8.html...
The plot thickens: There may be additional issues for WSL2 running in a VM host, like we're doing for our GitHub runners: https://tomssl.com/fixing-clock-drift-in-wsl2-using-windows-terminal/
I tried running the new **neon-clocksync** container in `DockerComposeFixture` before starting the application, but that didn't work.
This article might help: https://www.codeproject.com/Articles/5315010/How-to-Use-Certificates-in-ASP-NET-Core
Related or duplicate: #999