Fixed
Status Update
Comments
da...@gmail.com <da...@gmail.com> #2
Converting to an enhancement request.
wu...@google.com <wu...@google.com> #3
Any update on the status of this enhancement?
sc...@google.com <sc...@google.com> #4
Fails for UrlFetches to far-away places like China. Making it configurable would be useful -- or reporting it as an actual timeout would help as well.
sh...@google.com <sh...@google.com> #5
I also need this feature, any update on the status ?
da...@gmail.com <da...@gmail.com> #6
Any update?
da...@gmail.com <da...@gmail.com> #7
Any update on this feature request, Its really important for us to have this feature
sc...@google.com <sc...@google.com> #8
I'm seeing the opposite issue lately. The UrlFetchApp.fetch call is taking far too long, the worst today is 257sec. I'd like to set a 10-30sec timeout and stop these calls from using up all of my time-based quotas. There must be an issue with this function as manually calling these urls is much faster, typically a second or less.
tr...@google.com <tr...@google.com> #9
Yes, I need a configurable timeout to prevent a single long running fetch from eating up all the time-based quota.
sc...@google.com <sc...@google.com> #10
@ g...@websawin.com
I see the same bahaviour, that the timeout happens now after several minutes.
Also my UrlFetchApp.fetch() call aborted after more than 4 Minutes (!) today with an timeout!
According to the google error mail ("summary of failures of google apps script"), there must be also UrlFetchApp.fetch() calls taking more than 9 Minutes ("script exceeded maximum execution time").
This is consuming up all my daily CPU-time, very frustating :-((
I see the same bahaviour, that the timeout happens now after several minutes.
Also my UrlFetchApp.fetch() call aborted after more than 4 Minutes (!) today with an timeout!
According to the google error mail ("summary of failures of google apps script"), there must be also UrlFetchApp.fetch() calls taking more than 9 Minutes ("script exceeded maximum execution time").
This is consuming up all my daily CPU-time, very frustating :-((
mi...@google.com <mi...@google.com> #11
This would be a great feature, since max execution time for a trigger is 1h or 3h a day in pro plan and if a ressource doesn't respond it does eventually timeout after 5 minutes. It would be much better if we could timeout the request and try later to better optimize our ressources.
ap...@google.com <ap...@google.com> #12
Project: platform/frameworks/support
Branch: androidx-main
commit 874ef5abba7929d0110fd54392ae9d8ee91003f0
Author: mingdatsai <mingdatsai@google.com>
Date: Mon May 09 20:32:42 2022
Catch CameraCharacteristicsBaseImpl exceptions
Some devices may throw AssertionError, which is not the expected
behavior, when failed to get CameraCharacteristic. When that happens,
we catch the error and return null to workaround it.
Bug: 231701345
Test: ZoomControlTest, ZoomControlDeviceTest &
Camera2CameraControlImplDeviceTest
Change-Id: Ia248ae5580b9d4a0949f4448ccbafcedd1ba7b9b
M camera/camera-camera2/src/test/java/androidx/camera/camera2/internal/ZoomControlTest.java
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/ZoomControl.java
M camera/camera-camera2/src/androidTest/java/androidx/camera/camera2/internal/Camera2CameraControlImplDeviceTest.java
M camera/camera-camera2/src/androidTest/java/androidx/camera/camera2/internal/ZoomControlDeviceTest.java
https://android-review.googlesource.com/2092403
Branch: androidx-main
commit 874ef5abba7929d0110fd54392ae9d8ee91003f0
Author: mingdatsai <mingdatsai@google.com>
Date: Mon May 09 20:32:42 2022
Catch CameraCharacteristicsBaseImpl exceptions
Some devices may throw AssertionError, which is not the expected
behavior, when failed to get CameraCharacteristic. When that happens,
we catch the error and return null to workaround it.
Bug: 231701345
Test: ZoomControlTest, ZoomControlDeviceTest &
Camera2CameraControlImplDeviceTest
Change-Id: Ia248ae5580b9d4a0949f4448ccbafcedd1ba7b9b
M camera/camera-camera2/src/test/java/androidx/camera/camera2/internal/ZoomControlTest.java
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/ZoomControl.java
M camera/camera-camera2/src/androidTest/java/androidx/camera/camera2/internal/Camera2CameraControlImplDeviceTest.java
M camera/camera-camera2/src/androidTest/java/androidx/camera/camera2/internal/ZoomControlDeviceTest.java
da...@gmail.com <da...@gmail.com> #14
Any update on this feature request? Would help out a lot within a very large and important application. Thanks.
mi...@google.com <mi...@google.com> #15
yes, I need the same. Yes, please increase timeout to 5 mins at least.
ju...@google.com <ju...@google.com> #16
It's hard to take App Script as a serious framework when this basic functionality is missing...
Description
We're receiving these crash reports for our app on the Play Store (https://play.google.com/store/apps/details?id=app.grapheneos.camera.play ). I'm unsure why it's happening, but perhaps you can get one of these devices and reproduce it. Ideally, CameraX could at least start catching this exception and turning it into an error surfaced to the app.
We're mostly seeing these crashes from the Jio JioPhone Next which is a very widely used, very cheap device in India. The crash traceback is nearly identical across the around 5 device models where we've seen it with only minor variations in Camera2 implementation line numbers. All of the impacted devices are Android 11.