paul chipchase edc22944d3 Improve error reporting with the new error flow in VA ...

#rb PJ.Kack
#jira UE-180383
#rnx

- With the new error flow we block the process on a failed pull and then quit the process if the connection cannot be recovered, this means that we never reach the code that reports which payloads failed.
- Added similar reporting to FVirtualizationManager::OnPayloadPullError so we can get a log of which payloads failed to pull.
-- A pull failure should not really be dependant on the payload itself so this info isn't that important but it can be useful to eliminate potential issues by allowing us to confirm that the payload does in fact exist in persistent storage and the user was just unable to access it.

[CL 28833473 by paul chipchase in ue5-main branch]

2023-10-17 03:58:43 -04:00

..

Private

Improve error reporting with the new error flow in VA

2023-10-17 03:58:43 -04:00

Public

Prevent the VA error dialogs from being shown if the code is being run in a scenario where a user will not be present.

2023-09-25 06:48:33 -04:00

Virtualization.Build.cs

Now if the VA source control backend fails to connect we can display a dialog to the user asking for the correct credentials directly. Currently disabled by default.

2023-06-20 04:26:06 -04:00