Fixed
Status Update
Comments
be...@unity3d.com <be...@unity3d.com> #2
using the below does resolve the issue and allow the app to be deployed.
gcloud config set app/use_gsutil true
gcloud config set app/use_gsutil true
da...@gmail.com <da...@gmail.com> #3
Thanks for the update! We think we have a handle on this issue, and there should be a patch in the Cloud SDK 106 release due out next week that will work with the 'use_gsutil false' setting (which will eventually become the new default).
bg...@artnet.com <bg...@artnet.com> #4
Comment has been deleted.
[Deleted User] <[Deleted User]> #5
According to Google Cloud Support, there is a chance that this issue will be fixed in the January release of Cloud SDK.
ba...@gmail.com <ba...@gmail.com> #6
In case the proposed example will be used for fixing the bug, here is an alternative that uses the native PowerShell method:
$run_args_array += -Split $cloudsdk_python_args
$run_args_array += -Split $cloudsdk_python_args
gh...@google.com <gh...@google.com>
gh...@google.com <gh...@google.com> #7
Hello,
This has been forwarded to the Engineering Team so that they may evaluate it. Please note that there are no ETAs for this issue. All communication regarding this issue is to be done here.
se...@aclassmedicalsupplies.com <se...@aclassmedicalsupplies.com> #8
Has there been any updates connected to this issue?
cg...@google.com <cg...@google.com> #9
For posterity, this was fixed in the 413.0.0 release on 2023-01-10 (forgot to close this bug earlier).
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Customer reported this issue for PowerShell 7.3.0https://github.com/PowerShell/PowerShell/issues/18529
The problem is on line 109 in gcloud.ps1. Basically, on line 109 in gcloud.ps1:
this line should be changed to:
so that empty entries are not included. What happened previously is that the split resulted in empt entries, and these were passed to python.exe. However, due to a bug in how parameters are passed to native commands, empty strings would be silently removed. The fix in PowerShell 7.3.0 is to preserve empty args so you can do something like:
where you explicitly pass an empty string as a value to a parameter. With that change, empty args now get passed to python.exe which causes it to fail. The change here removes empty args that are not meaningful and will work across all versions of PowerShell (including Windows PowerShell 5.1).