Assigned
Status Update
Comments
sn...@diwala.io <sn...@diwala.io> #2
Both the code blocks are doing exactly same.
al...@gmail.com <al...@gmail.com> #3
The first does:
return getTotalLocalFileSize(f.listFiles()) + 1;
Instead of:
count += getTotalLocalFileSize(f.listFiles()) + 1;
for directories, which means it breaks the loop, ignoring the value of count and any other files or directories that might be in the array.
return getTotalLocalFileSize(f.listFiles()) + 1;
Instead of:
count += getTotalLocalFileSize(f.listFiles()) + 1;
for directories, which means it breaks the loop, ignoring the value of count and any other files or directories that might be in the array.
sa...@deloitte.com <sa...@deloitte.com> #5
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
- Android Gradle Plugin 8.8.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
th...@gmail.com <th...@gmail.com> #6
Guys , any updates,
Can we enable CORS using HTTPS Loadbalanacer
Can we enable CORS using HTTPS Loadbalanacer
zk...@gannett.com <zk...@gannett.com> #7
This ticket is about 2 years old now. Is there any update on this?
ja...@gmail.com <ja...@gmail.com> #8
Given that this effectively prohibits authenticated cloud function invocation from client code, can a gotcha please be made prominent in https://cloud.google.com/run/docs/authenticating/end-users and any other likely discovery points for authenticated cloud functions? This basically forces the use of unauthenticated access in order to use authentication, which is contradictory.
The wording inhttps://cloud.google.com/run/docs/authenticating/public of 'Use this option if your service is a public API or website.' should also be updated to include the case where 'Authorized' headers are provided, as these will trigger an OPTIONS request that will not succeed if authentication is enabled.
The wording in
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com>
sa...@hyphensocial.com <sa...@hyphensocial.com> #9
We need this!
Description
This is currently not available as the preflight OPTIONS request will always be rejected with status 403.
The Feature Request has already been routed to the Cloud Run engineering team and they are reviewing the request for possible future implementation. I cannot provide an ETA or guarantee of implementation, however, further updates will be shared here.