Wow, this is really great news I think.
I was under the impression that Google was phasing out the "legacy"
platform, so this is not the case?
A big relief for all of us sitting with a bunch of Java 8 services were
porting to second gen services is not really an option.
/ Linus
tisdag 4
Well, I can't write all code for you. Basically I would not advice you to
read and write potentially large video data files into memory. You will
probably
run out of memory. Lets walk thru your code:
see Channels java
doc:
How about
// Create your resource
BlobId blobId = BlobId.of(YOUR_BUCKET, *YOUR_FILENAME*);
BlobInfo blobInfo = BlobInfo.newBuilder(blobId).setContentType(*"video/mp4"*
).build();
Blob blob = getStorage().create(blobInfo);
WriteChannel writeChannel = blob.writer();
// Then use writeChannel to
For appengine std env the TaskQueue page in console has been removed,
instead you get redirected to the Cloud Task page. However before I can
visit that page I need to enable the Cloud Task api for my project.
AFAIK we are not yet forced to swap TaskQueues to CloudTasks, in fact
CloudTasks
I think I have seen some documentation way back that it was not possible to
serve user facing requests from a B instance, instead you
were supposed to dispatch the request to a TaskQueue and use some sort of
client polling in order to get notified when the work on B
instance was completed.
Cannot
Works again for me now.magic.
Den tor 8 okt. 2020 10:19troberti skrev:
> We have the same issue, for all our Appengine projects.
>
> On Wednesday, October 7, 2020 at 11:02:47 PM UTC+2 linus@gmail.com
> wrote:
>
>> In cloud console, Appengine Dasboard for a few days it says:
>>
>>
In cloud console, Appengine Dasboard for a few days it says:
Current load
This app has not received any requests in the last 24 hours.
This is obviously wrong since I have loads of requests in the logs and I
get billed for them as well.
This used to show the top 10 or 20 requested urls, is it
True story
One day in December some year ago customers called in complaining about our
service wasn't responding. A quick look in the console we could see that we
had gone over our spending limit. Why? Digging deeper we could see that we
had 1000+ instances running (standard, java, autoscale,
p engine
>> people, but not this one.
>>
>> 2. Google? Why am I getting this error now?
>>
>> 3. Can anybody else confirm that they can/cannot deploy using appcfg?
>>
>> Thanks
>>
>>
>>
>> On Thursday, May 14, 2020 at 7:29:49 PM UTC+12
I don't know about you guys, but I got this in the mail:
The legacy standalone App Engine SDK (appcfg) was deprecated as of *July
30, 2019*, in favor of the GA Cloud SDK
In java using std env you need to change the service (module) name to
"default" in appengine-web.xml, ex:
http://appengine.google.com/ns/1.0;>
your app
default
And of course change the name to another name on your current default module.
Should be simiular in other languages as
According to
https://cloud.google.com/appengine/docs/standard/java/release-notes the
possibility to alter the daily spending limit has been deprecated but
existing on will still be valid.
What happens if your service grows and the current spending limit is too
low? It has happen to us on
Totally agree, for small companies or startups with limited resources we
only want our services to run with minimal effort.
Den fredag 13 december 2019 kl. 15:02:52 UTC+1 skrev Joshua Smith:
>
> Confirmed that my deploy is now working. A little heads-up would be nice
> before you take another
Hi
The gcloud sdk has different package names for the datastore classes, ex:
com.google.cloud.datastore.Cursor.
I think you'll need to import the cloud datastore classes / client api.
Check the bookshelf example app pom / parent pom.
Den onsdag 27 november 2019 kl. 01:09:30 UTC+1 skrev Han
:18 UTC+1 skrev Linus Larsen:
>
> So basically what you are telling me is there is no way for me to get FCM
> messaging working with my existing app engine project that I have been
> running
> for more or less 4 years now?
>
> I tried the Firebase Admin SDK for java, bu
So basically what you are telling me is there is no way for me to get FCM
messaging working with my existing app engine project that I have been
running
for more or less 4 years now?
I tried the Firebase Admin SDK for java, but I cannot initialise the
library since I need a database name, I
It was pretty straight forward for me until I had to create the actual
database where there was an error saying in order to create a new database I
have to create a new project. Probably because my existing appengine standard
project already using cloud datastore. I guess thats fine, however
FK, I filed a feature
request, https://issuetracker.google.com/issues/114794562
Den tisdag 11 september 2018 kl. 15:07:53 UTC+2 skrev Linus Larsen:
>
> I'm using pubsub with batching and I wan't to be able to drain the queue
> on any pontential messages before the instance shutdown
I'm using pubsub with batching and I wan't to be able to drain the queue on
any pontential messages before the instance shutdown.
Piece of cake I thougt, just call shutdown() in
LifecycleManager.shutdown(), end of story. However I'm running my instances
with
autoscaling and there seems to be no
Do you have the same version number on the app running as the one you have
locally, if so one workaround can be to set another version number
on your local app. Run update, then enable the new version in the console
UI. However, if everything works ok, remember to delete the instances of the
old
Yep, this is really easy do reproduce in the standard env as well. Just
deploy a new version, migrate traffic to the new version. The
old version still keeps instances running (in my case both python and java).
Den måndag 26 februari 2018 kl. 15:49:58 UTC+1 skrev Hendrik Kleinwächter:
>
> We
Wow just got 60+ instances of my autoscaling service becuse of this, hope I
don't have to pay for them.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Is your app by any chance in europe-west region? There is a thread created
today about this, in short we got this answer from Google today:
"There was an issue with elevated error rate for Google App Engine Memcache
service for European applications which has been resolved for all affected
equests only but not all the time. We have bursts of a few
> hours, e.g. yesterday from 3pm to 9pm.
>
> Best
>
> Michael
>
>
> On Friday, July 28, 2017 at 9:28:19 AM UTC+2, Linus Larsen wrote:
>>
>> Latel
Lately I'm getting a lot of these (java, standard env):
com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler
handleApiProxyException: Memcache putAll: Unknown exception setting 1 keys:
Memcache is temporarily unavailable. (MemcacheServiceApiHelper.java:68
After some digging I found out that we've made some modifications on the
mobile app, which makes it do several ajax requests rapidly.
The result became somewhat strange.
1. Request1 starts a new instance
2. Request2 also starts a new instance since it takes aprox 20 secs to
start a new
Last couple of days our app has started to behave strange, seems like our
instances are shut down very rapidly. Our low traffic default instance
could easily manage a whole day with just a few instances, until a couple
of days ago. Now it starts around 100 instances a day for no apparent
at
>might be removing these headers?
>
> Any information you can provide to more effectively diagnose or reproduce
> the issue would be very helpful.
>
>
> On Saturday, March 12, 2016 at 6:06:50 AM UTC-5, Linus Larsen wrote:
>>
>> Sometime yesterday (10th),
ag 12 mars 2016 kl. 15:28:12 UTC+1 skrev Nickolas Daskalou:
>
> Hi Linus,
>
> Do you have a public URL we can test?
>
> Nick
> On 12/03/2016 10:07 PM, "Linus Larsen" <linus@gmail.com >
> wrote:
>
>> Sometime yesterday (10th), our clients star
Sometime yesterday (10th), our clients started to behave strage. After some
investigation it seems like Google decided to remove the Content-Length
header from the http responses. The request / response messages between our
clients are actually small protobuf encoded binary messages, using
30 matches
Mail list logo
