app/cloud_build_timeout doesn't seem to work for App Engine Standard Environment [131889237]

Assigned

Feature Request

Status Update

No update yet.

Description

ho...@gmail.com

created issue #1

May 3, 2019 02:13PM

Problem you have encountered:
I have an application running on App Engine Standard Environment using the Go 1.11 runtime.

https://cloud.google.com/appengine/docs/standard/go111/runtime

Running `gcloud app deploy` sometimes fails after 10 minutes with the following message:

```
ERROR: (gcloud.app.deploy) Error Response: [4] Cloud build did not succeed within 10m.
Build error details: Build error details not available..
Check the build log for errors:

https://console.cloud.google.com/gcr/builds/<build_id>?project=<project_id>
Exited with code 1
```

Following the link to Cloud Build, the build log ends with the following error:

```
TIMEOUT
ERROR: context deadline exceeded
```

Others have encounter similar issues (some with Go in particular, others in other context):

https://github.com/golang/go/issues/28046

https://stackoverflow.com/questions/50046545/google-app-engine-build-timed-out-during-deployment

https://groups.google.com/d/msg/google-appengine/Ed8DcqxIPPo/v6gkGWWiCAAJ

https://medium.com/@erdoganyesil/unknown-error-response-4-deadline-exceeded-2f0ad47b5215

All the workarounds points to the app/cloud_build_timeout option:

https://cloud.google.com/sdk/gcloud/reference/config/set#cloud_build_timeout

Based on my testing, changing this option doesn't actually do anything for my project. It seems like everyone else who used this option have used it in App Engine Flexible Environment, so I suspect that maybe this option doesn't do anything in Standard Environment?

What you expected to happen:
Running `gcloud config set app/cloud_build_timeout 1200` for an App Engine Standard Environment project running Go 1.11 to actually increase the build timeout to 20 minutes.

Steps to reproduce:
1. `gcloud config set app/cloud_build_timeout 1200`
2. `gcloud app deploy`
3. Deployment fails due to Cloud Build timeout after 10 minutes

Comments

ba...@google.com <ba...@google.com> #2May 22, 2019 03:42PM

Status: Won't Fix (Infeasible)

Project: platform/frameworks/support
Branch: androidx-main

commit b6c7c78f9e7476b468dafe9d5f7dec6794d47f09
Author: Shahd AbuDaghash <shahddaghash@google.com>
Date: Mon Nov 27 11:16:51 2023

Introduce DecayAnimation in AnchoredDraggable

Decay animation allows more realistic settling of a component. This is performed by now passing a `DecayAnimationSpec` parameter to AnchoredDraggable and using it when animating to the target. The new animation implementation will be added in a chain CL.

Bug: 288084801
Test: Tests will be added in a chain CL
Relnote: This change adds a `decayAnimationSpec` parameter to AnchoredDraggable allowing to use decay animation when settling to one of the anchors. The change also includes renaming the existing `animationSpec` to `snapAnimationSpec` to help understanding the use case of each spec.
Change-Id: I44ccd408d919328fd6504d31d8db59cf1d07de43

M compose/foundation/foundation/api/current.txt
M compose/foundation/foundation/api/restricted_current.txt
M compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/AnchoredDraggableSample.kt
M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableGestureTest.kt
M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableStateTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/AnchoredDraggable.kt

https://android-review.googlesource.com/2847074

da...@google.com <da...@google.com> #3Jul 15, 2019 08:27PM

Status: Assigned (reopened)

Project: platform/frameworks/support
Branch: androidx-main

commit 365993d1a90c27704b71f6bee042a1749314a4b1
Author: Shahd AbuDaghash <shahddaghash@google.com>
Date: Tue Nov 28 10:49:56 2023

Add tests for Animation in AnchoredDraggable

Added tests to check for different settling behaviors.

Bug: 288084801
Test: Added tests to verify behavior.
Change-Id: I369b30c69f7c29f676ae0671fef25c38ff3c74cb

M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableStateTest.kt

https://android-review.googlesource.com/2847475

da...@google.com <da...@google.com> #4Jul 15, 2019 08:38PM

Project: platform/frameworks/support
Branch: androidx-main

commit ff1a600df5f4d8ae21a75d8e3e0f24d6c5c2faee
Author: Shahd AbuDaghash <shahddaghash@google.com>
Date: Mon Nov 27 15:51:12 2023

Modify settle function to perform decay animation if possible

When settling, a check will be performed to see if natural decay animation can be used. If not so, a target animation will be used. The consumed velocity is returned to the settle function, which could be used to show an overscroll effect.

Bug: 288084801
Test: Tests will be added in a chain CL.
Relnote: This change introduces a new `animateToWithDecay` function that naturally decays if possible. It takes the target value and the initial velocity. The `animateTo` functions no longer takes a velocity, but passes the available velocity in `lastVelocity` to animation, as it is concerned with reaching the target. If users need to pass a certain velocity for animation, they can use `animateToWithDecay` function.
Change-Id: I465dbd826e3969b784d08c65425f4bbda3de8493

M compose/foundation/foundation/api/current.txt
M compose/foundation/foundation/api/restricted_current.txt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/AnchoredDraggable.kt

https://android-review.googlesource.com/2847576

Message last modified on Jul 16, 2019 03:58PM

jo...@mathsburst.com <jo...@mathsburst.com> #5Jul 15, 2019 10:31PM

Project: platform/frameworks/support
Branch: androidx-main

commit 01142ddd5b14eb33e5145c4e72e6619a5c100fe4
Author: Shahd AbuDaghash <shahddaghash@google.com>
Date: Thu Dec 21 12:34:00 2023

Introduce Overscroll in AnchoredDraggable

Adding overscroll support to AnchoredDraggable by giving the ability to pass a customized overscrollEffect object to AnchoredDraggable.

Bug: 288084801
Relnote: An OverscrollEffect has been introduced to allow for custom overscroll effects in anchoredDraggable. To retrieve the consumed velocity after animation, the consumed velocity is returned from the settle function.
Test: Added tests to verify behavior
Change-Id: I100683fe7473b1e5ff317ab22245a2b0a25bd549

M compose/foundation/foundation/api/current.txt
M compose/foundation/foundation/api/restricted_current.txt
M compose/foundation/foundation/integration-tests/foundation-demos/src/main/java/androidx/compose/foundation/demos/AnchoredDraggableDemo.kt
M compose/foundation/foundation/samples/src/main/java/androidx/compose/foundation/samples/AnchoredDraggableSample.kt
A compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableOverscrollTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/AnchoredDraggable.kt

https://android-review.googlesource.com/2888106

su...@google.com <su...@google.com> #6Oct 30, 2020 08:31AM

Project: platform/frameworks/support
Branch: androidx-main

commit 0f071d797bccf7eff2a23e408928ca76640af782
Author: Shahd AbuDaghash <shahddaghash@google.com>
Date: Wed Nov 29 18:34:09 2023

Migrates AnchoredDraggable to Modifier.Node

Migrates AnchoredDraggable to Modifier.Node. This helps in adding Overscroll effect in AnchoredDraggable.

Bug: 288084801
Test: Added tests to verify behavior
Change-Id: I3f3338cd71763972c4b70f2e06c97e85285b0035

M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableGestureTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/AnchoredDraggable.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/Draggable.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/Draggable2D.kt

https://android-review.googlesource.com/2852691

jo...@theinfatuation.com <jo...@theinfatuation.com> #7Nov 2, 2020 06:04PM

This issue is marked as fixed, but there is still no replacement for ResistanceConfig.

How should we properly migrate it?

al...@gmail.com <al...@gmail.com> #8Oct 9, 2021 08:49AM

Can we document this / update the migration guide?

jo...@lindy.ai <jo...@lindy.ai> #9Jan 14, 2022 08:01PM

+1 for being able to provide a timeout in the gcloud app deploy command. Where should we add that as a feature request?

si...@dynamite.ventures <si...@dynamite.ventures> #10Jul 25, 2022 10:37PM

+1

All of our deploys to AppEngine Standard are failing because of this for a few days now!

ab...@kaplan.com <ab...@kaplan.com> #11Aug 3, 2022 11:03AM

+1
Do we have any update on this feature request?

ne...@gmail.com <ne...@gmail.com> #12Aug 31, 2024 10:35PM

Same!!

ra...@gmail.com <ra...@gmail.com> #13Dec 17, 2024 09:20AM

Following up on 'timeout' setting for App Engine Standard Environment.
Let us know whether it is possible to have at least 60 minutes timeout per session, similar to how we can configure this on other cloud providers