Support Gradle incremental annotation processing [112110217]

Fixed

Feature Request

Status Update

No update yet.

Description

da...@google.com

created issue #1

Aug 1, 2018 11:57PM

See:

https://docs.gradle.org/nightly/userguide/java_plugin.html#sec:incremental_annotation_processing

Comments

da...@google.com <da...@google.com> #2Mar 15, 2019 05:56PM

Converting to an enhancement request.

to...@gmail.com <to...@gmail.com> #3Apr 12, 2019 09:13AM

Any update on the status of this enhancement?

se...@gmail.com <se...@gmail.com> #4Apr 12, 2019 09:16AM

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.

to...@gmail.com <to...@gmail.com> #5May 21, 2019 01:25PM

I also need this feature, any update on the status ?

da...@google.com <da...@google.com> #6May 21, 2019 03:33PM

Any update?

ap...@google.com <ap...@google.com> #7May 29, 2019 10:54PM

Any update on this feature request, Its really important for us to have this feature

ap...@google.com <ap...@google.com> #8May 30, 2019 06:10PM

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.

ap...@google.com <ap...@google.com> #9Jun 6, 2019 05:23PM

Yes, I need a configurable timeout to prevent a single long running fetch from eating up all the time-based quota.

ap...@google.com <ap...@google.com> #10Jun 7, 2019 07:15PM

@ 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 :-((

da...@google.com <da...@google.com> #11Jun 7, 2019 07:40PM

Marked as fixed.

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.

to...@avast.com <to...@avast.com> #12Jun 28, 2019 10:38AM

When will be some alpha or at least snapshot build with this support, please?

yb...@google.com <yb...@google.com> #13Jun 28, 2019 07:17PM

[Comment deleted]

mi...@gtempaccount.com <mi...@gtempaccount.com> #14Oct 10, 2019 05:19AM

Any update on this feature request? Would help out a lot within a very large and important application. Thanks.

mi...@gtempaccount.com <mi...@gtempaccount.com> #15Oct 10, 2019 05:30AM

yes, I need the same. Yes, please increase timeout to 5 mins at least.

co...@protonmail.com <co...@protonmail.com> #16Jan 23, 2020 07:03AM

It's hard to take App Script as a serious framework when this basic functionality is missing...

yb...@google.com <yb...@google.com> #17Jan 23, 2020 05:30PM

a single fetch that times out eats up a good chunk of the time quota and makes a script run slow. Time out needs to be configurable

ap...@google.com <ap...@google.com> #18Jun 18, 2020 05:41PM

[Comment deleted]

bl...@gmail.com <bl...@gmail.com> #19Aug 20, 2020 08:45AM

Would really need this enhancement too

bl...@gmail.com <bl...@gmail.com> #20Aug 20, 2020 08:46AM

Yes, please I need this too.

hu...@google.com <hu...@google.com> #21Sep 17, 2020 09:27PM

I need this functionality. We were moving our code from vba to google app script, now with this limitation we can´t.

hu...@google.com <hu...@google.com> #22Sep 17, 2020 09:33PM

Also need to be able to decrease this! When a website is down, the long timeouts can kill the computer time quota for the day, rendering my script useless!