PSU 4.2.19 - Git certificate check failure during service launch

PowerShell Universal
1

During the service launch, following a reboot necessitated by the upgrade from 4.2.18 to 4.2.19, there is a log entry in PSU stating that an unknown certificate check failed. Looking in the system logs, I can see 8 lines revolving around this error.

2024-04-23 08:47:03.007 -04:00 [ERR] Failed to sync: unknown certificate check failure    at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in C:\actions-runner\_work\universal\universal\src\libgit2sharp\LibGit2Sharp\Core\Ensure.cs:line 154
   at LibGit2Sharp.Core.Ensure.ZeroResult(Int32 result) in C:\actions-runner\_work\universal\universal\src\libgit2sharp\LibGit2Sharp\Core\Ensure.cs:line 172
   at LibGit2Sharp.Core.Proxy.git_remote_fetch(RemoteHandle remote, IEnumerable`1 refSpecs, GitFetchOptions fetchOptions, String logMessage) in C:\actions-runner\_work\universal\universal\src\libgit2sharp\LibGit2Sharp\Core\Proxy.cs:line 2289
   at LibGit2Sharp.Commands.Fetch(Repository repository, String remote, IEnumerable`1 refspecs, FetchOptions options, String logMessage) in C:\actions-runner\_work\universal\universal\src\libgit2sharp\LibGit2Sharp\Commands\Fetch.cs:line 80
   at LibGit2Sharp.Commands.Pull(Repository repository, Signature merger, PullOptions options) in C:\actions-runner\_work\universal\universal\src\libgit2sharp\LibGit2Sharp\Commands\Pull.cs:line 37
   at UniversalAutomation.Git.GitService.Pull() in C:\actions-runner\_work\universal\universal\src\Universal.Server\Services\GitService.cs:line 683
   at UniversalAutomation.GitSyncService.TrySync(GitStatus status, Boolean force, GitSettings settings) in C:\actions-runner\_work\universal\universal\src\Universal.Server\Services\GitSyncService.cs:line 190
   at UniversalAutomation.GitSyncService.Sync(Boolean force) in C:\actions-runner\_work\universal\universal\src\Universal.Server\Services\GitSyncService.cs:line 104

I’m not sure if this is already known or expected, but the Git sync process does still work. So, this leads me to believe it’s some sort of a race condition, where a sync is attempting to be performed before the server and service are fully loaded.

Product: PowerShell Universal
Version: 4.2.19