paul chipchase fd77942248 We no longer consider failing to restore the original workspace as a fatal error when submitting virtualized payloads to perforce., ...

#rb trivial
#jira UE-160083
#rnx
#preflight 62f64714185b21882a875427

- When this backend was written, it shared the source control provider interface with the rest of the editor, so if we were unable to restore the workspace it would likely break the editor in interesting and hard to diagnose ways.
- Given the scope for problems and the low change of the operatation I opted to make the error fatal.
- Now that the backend owned it's own source control provider interface, the worst thing that can happen is that future virtualization attempts will also fail, but the user will not be left with a non functioning editor. With this in mind there is no longer a reason to consider this a fatal failure.

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

2022-08-12 08:45:08 -04:00

..

Private

We no longer consider failing to restore the original workspace as a fatal error when submitting virtualized payloads to perforce.,

2022-08-12 08:45:08 -04:00

Public

Fix UE_REGISTER_VIRTUALIZATION_BACKEND_FACTORY_LEGACY_IMPL to work correctly on none MSVC platforms

2022-08-11 10:28:39 -04:00

Virtualization.Build.cs

Give improved error messages to the user if the source control asset virtualization backend fails to connect.

2022-01-18 04:50:38 -05:00