Fix issue with blaze sync removing remote python SDK.
This is not testable because remote python SDK creation is an UE only feature,
and we compile against the CE python SDK. We can test for it, but not create one.
@@ -239,6 +239,8 @@ public class BlazePythonSyncPlugin implements BlazeSyncPlugin {
return false;
}
+ // Only check home path if SDK is local (i.e., not remote).
+ if (!PythonSdkUtil.isRemote(sdk)) {
// If an SDK exists with a home path that doesn't exist anymore, it's not valid
String sdkHome = sdk.getHomePath();
if (sdkHome == null) {
@@ -248,6 +250,7 @@ public class BlazePythonSyncPlugin implements BlazeSyncPlugin {
if (!sdkHomeFile.exists()) {
return false;
}
+ }
// Allow PySdkSuggester extensions the ability to veto an SDK as deprecated
return !isDeprecatedPythonSdk(sdk);
