Re: [google-appengine] Re: Minimize Frontend Instance Hours

[Giuliano Ribeiro]

In my case I included only this:


automatic_scaling:
   max_instances: 1

This will make sure I will have an entire day on free tier.




On Mon, Apr 6, 2020 at 8:09 PM Vitaly Bogomolov  wrote:

> Hi Matt
>
>
>> automatic_scaling:
>>   max_instances: 1
>>   min_instances: 0
>>
>
> automatic_scaling:
>   max_idle_instances: 1
>   min_idle_instances: 1
>
> WBR, Vitaly
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/7a5efc52-d5d4-4c19-9b62-e421d7c036d7%40googlegroups.com
> 
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFFKEc217UTk%2B04vaQd-%3DLnmkPtC%2BpjRak2LMExehxu1%2Bmsz_Q%40mail.gmail.com.

Re: [google-appengine] Re: Diving into App Engine is soooooooooooo hard now - My analysis

[Giuliano Ribeiro]

Unfortunately I need to say the same.
Nowadays, it seems Google is forcing us to use GKE or Cloud Run, as all the
App Engine "magic" gone.
I've been using App Engine my last 8years, and is clear, the Google
strategy is not App Engine anymore.



Giuliano Ribeiro
Cloud and Software



On Fri, Mar 20, 2020 at 1:11 AM john  wrote:

> +1
> I also lament the loss of the turnkey environment that app engine used to
> provide. I can only presume that the business model for it isn’t very
> profitable, otherwise someone else would reproduce it.
>
>
> On Monday, March 16, 2020 at 2:47:25 AM UTC-4, Nickolas Daskalou wrote:
>>
>> Same experience for us.
>>
>> 10 years ago App Engine was a revolution. Now it's almost revolting.
>>
>> Agree with the hard to set up development environment for the newer App
>> Engine installments.
>>
>> Other pain points too, like no shared Memcache replacement (we're told
>> NDB for Python 3 is fully ready, when in reality a lot of existing apps
>> which rely on the built in feature of the free shared Memcache will either
>> suffer performance issues and/or an increase in billing cost if they switch
>> over).
>>
>> Google are having a hard time working out how to crack the cloud
>> computing market. Enterprises go with Azure because Microsoft are already
>> heavily embedded and sell the business fluff well, and AWS have a massive
>> head start on startups due to a larger existing user base and service
>> offering because they were first in the game.
>>
>> Nick
>>
>> On Mon, 16 Mar 2020, 4:35 am Matthew Parkes,  wrote:
>>
>>> I have to totally agree with this.  My experience has been the same
>>> coming from AppEngine Standard python 2.7 I decided to try and migrate one
>>> of my apps to Python3.7 but was extremely frustrated and put off with the
>>> whole experience.  I lost a lot of nice framework that made decisions easy
>>> and straight forward to actually just get functionality working. (Endpoints
>>> API, User management, Data management, Admin datastore).  I found it very
>>> hard to get an actual development environment setup where I could rapidly
>>> develop and test, see data in the database etc.
>>>
>>> The local testing has become very difficult. It's sad that while google
>>> appears to say "Oh AppEngine so much more flexible for you now" sounds like
>>> a step forward, when really it's more like 1 step forward, 5 steps
>>> backwards.
>>>
>>> Disappointed,
>>>
>>> Matt
>>>
>>> On Sunday, 15 March 2020 08:48:56 UTC-7, Brian Ruuska wrote:
>>>>
>>>> Glad to hear I'm not the only one disappointed with it all. I started
>>>> using App Engine when it was in beta, and launched a one-person business
>>>> when it went GA. It's so overwhelming attempting to port my product to the
>>>> new environments that it's much more than a one-person effort. And with all
>>>> the land mines and missing functionality I decided to just close the
>>>> business last year. They seem to be more interested in serving big
>>>> enterprises, and us little guys are just left behind. :-(
>>>>
>>>> On Saturday, March 14, 2020 at 7:22:15 AM UTC-5, Kaan Soral wrote:
>>>>>
>>>>> I'll whine a lot, but there's a concentrated and crisp TL;DR in the end
>>>>>
>>>>>
>>>>> I've been using App Engine I guess for 10 years now? It's hard for me
>>>>> too, but also, I'm preparing to open source my current project, at each
>>>>> step I question everything, I was going to open source my game so young
>>>>> developers/kids/gamers could dive into networked game development easier
>>>>> (It's an MMORPG on Google Cloud, my dream was that open sourcing it could
>>>>> enable fast experimentation with the genre), but as it is, at the current
>>>>> state of App Engine, the bottleneck is definitely all the diversified and
>>>>> separated products, separate emulators (missing ones), separate 
>>>>> environment
>>>>> variables for everything etc. - I can't imagine a happy scenario where one
>>>>> could just develop an App Engine app locally without spending weeks trying
>>>>> to understand what's what first - Back in the day, I think the Launcher 
>>>>> GUI
>>>>> and the simplicity of it all, got us all hooked (This is coming

Re: [google-appengine] Cloudtasks handler auth in Go 1.12 standard env

[Giuliano Ribeiro]

I've done this filtering the request headers like described here:
https://cloud.google.com/appengine/docs/standard/go112/scheduling-jobs-with-cron-yaml#validating_cron_requests

Requests from the Cron Service will also contain a HTTP header:

X-Appengine-Cron: true



Giuliano Ribeiro



On Wed, Aug 28, 2019 at 12:52 AM Bob Glickstein 
wrote:

> I'm using the Go 1.12 standard environment. I have some handlers for cron-
> and cloudtasks-generated requests. How should these handlers ensure that
> requests are coming from my GAE service account? The docs are super unclear
> about this, and many are outdated (still referring to e.g. login: admin
> in app.yaml.)
>
> Thanks in advance!
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/360363bf-cdfd-4a1f-b036-5fdba04bd33d%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/360363bf-cdfd-4a1f-b036-5fdba04bd33d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFFKEc3P14ZAeuNwWhAj1-nyeMOatu%3Dq8om6JGeqJTy-99uugA%40mail.gmail.com.

[google-appengine] Re: Back to GAE after some years

[Giuliano Ribeiro]

Hi Roberto, welcome back to GAE!
I can give you my opinion for NDB part:

It's only supported on Python 2.7 runtime, not anymore on python 3, which 
is the AppEngine 2nd generation (using gVisor). 
As they want to have a "pure" runtime in the 2nd generation, it will not be 
ported. Recommended to use Datastore API.


Best regards,


On Wednesday, August 22, 2018 at 2:13:58 PM UTC+1, Roberto Martino wrote:
>
> Hi
> Four years ago, I created a complete application using GAE. This 
> appication is still in use.
> I was very happy with GAE and now, getting back to GAE now, I expect the 
> same experience, but it seems that many things are changed, also the 
> documentation changed a lot.
> I'm interested in using Python 3.x
>
> I'd love if anyone can correct me if I'm wrong and answer my questions.
>
> Database
> - blobstore -> deprecated, not a problem I see the alternative
>
> - datastore -> I enjoyed very much the philosophy behind Datastore and NDB.
> has NDB been substitued by Cloud Datastore Client Libraries or can I 
> still use NDB or is there any other best practice?
>
> Android and iPhone App
>
> Push Notifications
> -I used GCM for Android  Notifications and a custom python library for 
> Apple notifications -> deprecated
>I understand that now I must use Firebase.
>Can I use Firebase only for the Push Notifications and keep using 
> Datastore for the DB?
>
> Mobile  comunication, this is an important point for me.
> -I used Google Cloud Endpoints, very nice, very useful and fast for 
> building mobile devices comunication
>Is this still the best way for mobile comunication?
>I red that it does not works with python 3.x, will it be ported shortly?
>
> Thank you in advance
> Roberto
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2ba2c061-859d-47f3-8f00-768e62de4c59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: python 3.7 standard runtime release schedule?

[Giuliano Ribeiro]

It seems to be launched right now:
https://cloud.google.com/blog/products/gcp/introducing-app-engine-second-generation-runtimes-and-python-3-7


On Wednesday, August 8, 2018 at 6:30:16 PM UTC+1, Eric G wrote:
>
> Is there a document that describes the differences between Python 3 
> standard and flex?   At a quick glance at least the interface for Python 3 
> standard looks very similar to flex.  Thanks.
>>
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6d58fb40-973d-4933-9c41-c750e08e7063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine group

[Giuliano Ribeiro]

Yes, it is moderated.

_
Giuliano


On Mon, Aug 6, 2018 at 2:07 PM Steve Neal  wrote:

> Hi,
>
> Can you tell me if this group is moderated please?
>
> I've tried twice to post a question and it's not visible.
>
> Thanks, Steve.
>
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CAGw%2BpadXaYAj326cwHnWG8e6h%2BkBbdQga93iOKFCXAh8%3DLEuvA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFFKEc20MNKyz%2BxcsPN%3DS_czu91K%2BwKD3qKhuw4Kb4bfYiAB_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[Giuliano Ribeiro]

It's on Flex, right ?

As the Flex requires an answer on the default port, have you sure your app 
is running at least on the local development env ?




On Friday, July 6, 2018 at 6:30:00 PM UTC+1, yi he wrote:
>
> Thanks Giuliano,
>
> I saw some failures.
>
> A  INFO: End of request or previous flush has not yet completed, blocking.
>  
> A  Jul 06, 2018 5:14:44 PM com.google.apphosting.vmruntime.VmApiProxyDelegate 
> runSyncCall
>  
>
> A  INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : 
> APP_ERROR(2)
>
> 018-07-06 12:14:44.000 CDT 
>
> INFO: Error body: RPC Error: /StubbyService.Send to (unknown) : 
> APP_ERROR(2)
> Expand all | Collapse all
> {
> insertId: "1l61xvbf9j89do"  
> labels: {…}  
> logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
> receiveTimestamp: "2018-07-06T17:14:44.240478404Z"  
> resource: {…}  
> textPayload: "INFO: Error body: RPC Error: /StubbyService.Send to 
> (unknown) : APP_ERROR(2) "  
> timestamp: "2018-07-06T17:14:44Z"  
> }
>
>
>
> 2018-07-06 12:14:44.000 CDTjava.util.concurrent.ExecutionException: 
> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
> application server failed for the call logservice.Flush(). at 
> java.util.concurrent.FutureTask.report(FutureTask.java:122) at 
> java.util.concurrent.FutureTask.get(FutureTask.java:206) at 
> com.google.apphosting.vmruntime.VmAppLogsWriter.waitForCurrentFlush(VmAppLogsWriter.java:226)
>  at 
> com.google.apphosting.vmruntime.VmAppLogsWriter.flushAndWait(VmAppLogsWriter.java:211)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyEnvironment.flushLogs(VmApiProxyEnvironment.java:508)
>  at 
> com.google.apphosting.vmruntime.VmRuntimeUtils.flushLogsAndAddHeader(VmRuntimeUtils.java:109)
>  at 
> com.google.apphosting.vmruntime.jetty9.VmRuntimeWebAppContext.doScope(VmRuntimeWebAppContext.java:323)
>  at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) 
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>  at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
>  at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)
>  at org.eclipse.jetty.server.Server.handle(Server.java:517) at 
> org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:306) at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) 
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)
>  at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at 
> org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)
>  at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)
>  at 
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)
>  at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
>  at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
>  at java.lang.Thread.run(Thread.java:745) Caused by: 
> com.google.apphosting.api.ApiProxy$RPCFailedException: The remote RPC to the 
> application server failed for the call logservice.Flush(). at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.runSyncCall(VmApiProxyDelegate.java:175)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.makeApiCall(VmApiProxyDelegate.java:155)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate.access$000(VmApiProxyDelegate.java:75)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:434)
>  at 
> com.google.apphosting.vmruntime.VmApiProxyDelegate$MakeSyncCall.call(VmApiProxyDelegate.java:410)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  ... 1 more
>
> 2018-07-06 12:14:44.000 CDT2018-07-06 
> 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: Stopped 
> ServerConnector@43184193{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
> Expand all | Collapse all
> {
>  insertId: "1r9ki5zf9mcqwx"  
>  labels: {…}  
>  logName: "projects/triage/logs/appengine.googleapis.com%2Fstderr"  
>  receiveTimestamp: "2018-07-06T17:14:45.895354407Z"  
>  resource: {…}  
>  textPayload: "2018-07-06 17:14:44.933:INFO:oejs.ServerConnector:Thread-1: 
> Stopped ServerConnector@43184193{HTTP/1.1,[http/1.1]}

[google-appengine] Re: Google App Engine. Start from last week, keep responding 503 error.

[Giuliano Ribeiro]

Hi Yi, 

do you took a look on StackDrive logging? Any issues on the instances 
startup?



On Friday, July 6, 2018 at 5:31:50 PM UTC+1, yi he wrote:
>
> Hello,
> I met a issue.
> Everything works fine at the begin of this week. In the middle of the 
> week, user reported can not access the website and I found the server 
> respond 503 error. 
> Do you have any guide how to locate the root cause?
> I tried to redeploy it. It worked last night and broken again this morning.
>
> Thanks.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/59504a79-06ab-4fd5-beb0-2158af7d8297%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: scheduling job using cron.xml in google app engine

[Giuliano Ribeiro]

Hi, have you read more about this here:
https://cloud.google.com/appengine/docs/standard/java/config/cronref#custom

I haven't found a example like you want and I guess it is not possible.

Take a look on the documentation page.


On Sunday, June 24, 2018 at 9:05:39 AM UTC+1, abhishek grover wrote:
>
> Hi All,
>
> Can anyone help me on how to schedule job using cron.xml.
> My requirement is to schedule job every 2 min  from 09:00 to 10:00 in 
> weekdays.
> As per the google docs i have come up with below schedule format.
> But this format will schedule job for weekend also.
> So can anyone tell me how to add the weekday option in below format.
>
>every 2 minutes from 09:00 to 10:00
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/027ffa09-c1ab-45bf-9e0b-0504e1baa463%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Servidor hakeado

[Giuliano Ribeiro]

For all of you guys that are not understanding, this thread is in Brazilian 
portuguese and the problem is not related to App Engine.




On Sunday, June 24, 2018 at 7:14:43 PM UTC+1, Giuliano Ribeiro wrote:
>
> Olá Raphaela, 
> então, realmente este não seria o local adequado, pois aqui é o Forum do 
> App Engine, plataforma como serviço do Google Cloud.
>
> Mas já te orientando, isso que aconteceu no seu servidor é uma prática 
> chamada ransomware. Infelizmente se tu não tiver backup feito por ti mesmo, 
> o suporte do Google Cloud não tem como te ajudar não. Pois como a máquina é 
> tua, a Google deixa toda a responsabilidade na tuas mão.
>
> Mas mesmo assim, tenta algum contato nos Fórums do Compute Engine.
>
>
>
> On Sunday, June 24, 2018 at 4:32:22 PM UTC+1, raphaelan...@gmail.com 
> wrote:
>>
>> Ola Giuliano estou meio perdida , eu tenho um servidor na google cloud , 
>> e recentemente meu servidor foi invadido , não sei se estou postando no 
>> lugar certo mais preciso de ajuda caso eu esteja no lugar errado por favor 
>> me oriente onde posso conseguir ajuda.
>>
>> eu tenho um servidor windows server 2012 e os arquivos  foram todos 
>> criptografados.
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4ac6d4a8-2be4-4631-bd83-dfb5953444f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Servidor hakeado

[Giuliano Ribeiro]

Olá Raphaela, 
então, realmente este não seria o local adequado, pois aqui é o Forum do 
App Engine, plataforma como serviço do Google Cloud.

Mas já te orientando, isso que aconteceu no seu servidor é uma prática 
chamada ransomware. Infelizmente se tu não tiver backup feito por ti mesmo, 
o suporte do Google Cloud não tem como te ajudar não. Pois como a máquina é 
tua, a Google deixa toda a responsabilidade na tuas mão.

Mas mesmo assim, tenta algum contato nos Fórums do Compute Engine.



On Sunday, June 24, 2018 at 4:32:22 PM UTC+1, raphaelan...@gmail.com wrote:
>
> Ola Giuliano estou meio perdida , eu tenho um servidor na google cloud , e 
> recentemente meu servidor foi invadido , não sei se estou postando no lugar 
> certo mais preciso de ajuda caso eu esteja no lugar errado por favor me 
> oriente onde posso conseguir ajuda.
>
> eu tenho um servidor windows server 2012 e os arquivos  foram todos 
> criptografados.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/16cc26e0-e6bd-4408-bee7-30c449c21d35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Servidor hakeado

[Giuliano Ribeiro]

Olá Raphaela, explique o que aconteceu. Pois o App Engine é serverless não
acessamos o servidor. Está usando o standard out o flex?



___
Giuliano Ribeiro

Em Sáb, 23 de jun de 2018 16:59,  escreveu:

>
> Preciso de ajuda de vocês meu servidor foi hackeado e não sei oque fazer
> se tem como fazer roll back de algum dia anterior se tem alguma coisa para
> fazer para me defender preciso de ajuda!
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/022ae1a6-e8ff-4eed-a1ed-aeddda02826a%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/022ae1a6-e8ff-4eed-a1ed-aeddda02826a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAFFKEc0TL5RNR15RBYdH3or%2Bs4E-Lzc7rQsoMzrEDbcUrs2Guw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Migrate to Java 8 runtime

[Giuliano Ribeiro]

I faced it some time ago, you should not us the repackaged import.
Just change the import to com.google.gson.* (and of course, include the 
gson lib on gradle)



On Friday, June 1, 2018 at 2:25:16 PM UTC+1, Carlos Lee wrote:
>
> Thanxs for your help George.
>
>
> I'm working on this migration task. Sorry to bother, I also need one more 
> help.
>
> In my backend, I'm using two imports: 
> import com.google.appengine.repackaged.com.google.gson.Gson;
> import com.google.appengine.repackaged.com.google.gson.GsonBuilder;
> ...
> Gson gson = new GsonBuilder().create();
>
>
> ...
>
> After I changed runtime to java8: java8 in 
> appengine-web.xml
>
> this line: Gson gson = new GsonBuilder().create();
>
> started to have:
> java.lang.NoClassDefFoundError: 
> com/google/appengine/repackaged/com/google/gson/GsonBuilder
>
>1. 
>   1. at frolic.br.brainexercises.backend.MyEndpoint.getGameRankingV2 
>   (MyEndpoint.java:228)
>
>
>
> Do you have any clue why I started to have this issue?
>
> Regards
>
> Carlos Eduardo Ki Lee
>
>
> Em quinta-feira, 31 de maio de 2018 19:15:18 UTC-3, George (Cloud Platform 
> Support) escreveu:
>>
>> Hello Carlos, 
>>
>> You are right, you should follow the appropriate document. 
>>
>> The statements you look for are: 
>>
>> sourceCompatibility = 1.8 // App Engine Flexible uses Java 8
>> targetCompatibility = 1.8 // App Engine Flexible uses Java 8
>>
>> More detail may be gathered from the "Creating a new Gradle project" 
>> sub-chapter 
>> 
>>  
>> of the "Using Gradle and the App Engine Plugin" online document. 
>>
>
-- 
 


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0dfeda9b-3133-4dae-9a09-7a41307d82cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dev_appserver now compatible with Cloud Datastore Emulator.

[Giuliano Ribeiro]

When I setup the local env, see the log:
WARNING  2018-06-01 13:21:25,741 api_server.py:581] Detected environment 
variable DATASTORE_EMULATOR_HOST=localhost:, dev_appserver will speak 
to the Cloud Datastore emulator running on this address. The datastore_path 
/var/folders/n4/vq69gqrn3470jyqdp1sxp2wwgn/T/appengine.None.gribeiro/datastore.db
 
will be neglected.
If you want datastore to store on 
/var/folders/n4/vq69gqrn3470jyqdp1sxp2wwgn/T/appengine.None.gribeiro/datastore.db,
 
remove DATASTORE_EMULATOR_HOST from environment variables and restart 
dev_appserver

And my app still writing/reading from the cloud.

On Wednesday, May 30, 2018 at 6:55:32 PM UTC+1, Kai Wang wrote:
>
> According to the documentation 
> <https://cloud.google.com/datastore/docs/tools/datastore-emulator#setting_environment_variables>,
>  
> you need to have the env var "DATASTORE_EMUALTOR_HOST" set. 
>
> Also, FYI, this "cloud.google.com/go/datastore" (officially, it is called 
> Google Cloud Client Library), should be able to connect to the datatore 
> emulator, no matter the code runs inside or outside of the dev_appserver.
>
> Please check the env var and lmk if they work :)
>
> On Wednesday, May 30, 2018 at 6:39:05 AM UTC-7, Giuliano Ribeiro wrote:
>>
>> Hi Kai Wang, I'm using "cloud.google.com/go/datastore"
>> As I read in the documentation this datastore package support the 
>> emulator, I was thinking it should be easy to use. But even enabling the 
>> emulator in the dev_appserver, my app is reading and writing directly in 
>> the cloud, ignoring the emulator. 
>>
>> Thanks,
>>
>> On Tuesday, May 29, 2018 at 8:08:08 PM UTC+1, Kai Wang wrote:
>>>
>>> Hi Glullano,
>>>
>>> What go libraries are you using? Is it 
>>> google.golang.org/appengine/datastore (link 
>>> <https://cloud.google.com/appengine/docs/standard/go/datastore/reference>) 
>>> ?
>>> Did it store locally before?
>>>
>>> You can email  k...@google.com for further details :)
>>>
>>>
>>> On Friday, May 25, 2018 at 9:04:42 AM UTC-7, Giuliano Ribeiro wrote:
>>>>
>>>> Really nice, but how to put it to work ?
>>>> I'm using with Go, even setting up to true, my app still saving data in 
>>>> the cloud.
>>>>
>>>> Thank you, 
>>>>
>>>>
>>>> On Wednesday, May 16, 2018 at 9:57:42 PM UTC+1, Steren Giannini wrote:
>>>>>
>>>>> Dear App Engine users,
>>>>>
>>>>> We are pleased to announce that the App Engine local development 
>>>>> server (dev_appserver) is now compatible with the Cloud Datastore 
>>>>> Emulator 
>>>>> <https://cloud.google.com/datastore/docs/tools/datastore-emulator>.
>>>>>
>>>>> You can opt-in to this feature by running:
>>>>> * dev_appserver.py --support_datastore_emulator*
>>>>>
>>>>> By using the --support_datastore_emulator flag, dev_appserver will use 
>>>>> Cloud Datastore Emulator for local datastore emulation. You can read more 
>>>>> about the migration process here 
>>>>> <https://cloud.google.com/appengine/docs/standard/python/tools/migrate-cloud-datastore-emulator>
>>>>> .
>>>>> The development server and Cloud Datastore Emulator support the 
>>>>> interoperation of ndb and Cloud Datastore client libraries. 
>>>>>
>>>>> Please help us test this feature. Our goal is to enable it by default 
>>>>> in the future.
>>>>> Please share your feedback by replying directly to this thread. We are 
>>>>> looking forward to it!
>>>>>
>>>>> Thanks,
>>>>> Steren
>>>>> Product Manager
>>>>> Google Cloud
>>>>>
>>>>
>>>>
>>>> <https://lp.google-mkto.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdNM09UQTVOek0wWmpabSIsInQiOiJLTUp1dEptSzBXaVF3WmNFd3FMTGdJN2swY3dCNUFlNmVrOWVZWllxXC95OHVEdGRacHhkUmxZRkZOXC9TbEx4bkhWRnlES3RrU1hlWkVkMEFudkdMb1h3PT0ifQ%3D%3D>
>>>
>>>
>>
>> <https://lp.google-mkto.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdNM09UQTVOek0wWmpabSIsInQiOiJLTUp1dEptSzBXaVF3WmNFd3FMTGdJN2swY3dCNUFlNmVrOWVZWllxXC95OHVEdGRacHhkUmxZRkZOXC9TbEx4bkhWRnlES3RrU1hlWkVkMEFudkdMb1h3PT0ifQ%3D%3D>
>
>
-- 
 
<https://lp.google-mkto.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdNM09UQTVOek0wWmpabSIsInQiOiJLTUp1dEptSzBXaVF3WmNFd3FMTGdJN2swY3dCNUFlNmVrOWVZWllxXC95OHVEdGRacHhkUmxZRkZOXC9TbEx4bkhWRnlES3RrU1hlWkVkMEFudkdMb1h3PT0ifQ%3D%3D>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/edfbf328-bab1-47ce-9e39-9f5734229582%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dev_appserver now compatible with Cloud Datastore Emulator.

[Giuliano Ribeiro]

Hi Kai Wang, I'm using "cloud.google.com/go/datastore"
As I read in the documentation this datastore package support the emulator, 
I was thinking it should be easy to use. But even enabling the emulator in 
the dev_appserver, my app is reading and writing directly in the cloud, 
ignoring the emulator. 

Thanks,

On Tuesday, May 29, 2018 at 8:08:08 PM UTC+1, Kai Wang wrote:
>
> Hi Glullano,
>
> What go libraries are you using? Is it 
> google.golang.org/appengine/datastore (link 
> <https://cloud.google.com/appengine/docs/standard/go/datastore/reference>) 
> ?
> Did it store locally before?
>
> You can email  k...@google.com  for further details :)
>
>
> On Friday, May 25, 2018 at 9:04:42 AM UTC-7, Giuliano Ribeiro wrote:
>>
>> Really nice, but how to put it to work ?
>> I'm using with Go, even setting up to true, my app still saving data in 
>> the cloud.
>>
>> Thank you, 
>>
>>
>> On Wednesday, May 16, 2018 at 9:57:42 PM UTC+1, Steren Giannini wrote:
>>>
>>> Dear App Engine users,
>>>
>>> We are pleased to announce that the App Engine local development server 
>>> (dev_appserver) is now compatible with the Cloud Datastore Emulator 
>>> <https://cloud.google.com/datastore/docs/tools/datastore-emulator>.
>>>
>>> You can opt-in to this feature by running:
>>> * dev_appserver.py --support_datastore_emulator*
>>>
>>> By using the --support_datastore_emulator flag, dev_appserver will use 
>>> Cloud Datastore Emulator for local datastore emulation. You can read more 
>>> about the migration process here 
>>> <https://cloud.google.com/appengine/docs/standard/python/tools/migrate-cloud-datastore-emulator>
>>> .
>>> The development server and Cloud Datastore Emulator support the 
>>> interoperation of ndb and Cloud Datastore client libraries. 
>>>
>>> Please help us test this feature. Our goal is to enable it by default in 
>>> the future.
>>> Please share your feedback by replying directly to this thread. We are 
>>> looking forward to it!
>>>
>>> Thanks,
>>> Steren
>>> Product Manager
>>> Google Cloud
>>>
>>
>>
>> <https://lp.google-mkto.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdNM09UQTVOek0wWmpabSIsInQiOiJLTUp1dEptSzBXaVF3WmNFd3FMTGdJN2swY3dCNUFlNmVrOWVZWllxXC95OHVEdGRacHhkUmxZRkZOXC9TbEx4bkhWRnlES3RrU1hlWkVkMEFudkdMb1h3PT0ifQ%3D%3D>
>
>
-- 
 
<https://lp.google-mkto.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiWkdNM09UQTVOek0wWmpabSIsInQiOiJLTUp1dEptSzBXaVF3WmNFd3FMTGdJN2swY3dCNUFlNmVrOWVZWllxXC95OHVEdGRacHhkUmxZRkZOXC9TbEx4bkhWRnlES3RrU1hlWkVkMEFudkdMb1h3PT0ifQ%3D%3D>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8235f0f4-f6b4-4841-b19f-be271f61f96a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: dev_appserver now compatible with Cloud Datastore Emulator.

[Giuliano Ribeiro]

Really nice, but how to put it to work ?
I'm using with Go, even setting up to true, my app still saving data in the 
cloud.

Thank you, 


On Wednesday, May 16, 2018 at 9:57:42 PM UTC+1, Steren Giannini wrote:
>
> Dear App Engine users,
>
> We are pleased to announce that the App Engine local development server 
> (dev_appserver) is now compatible with the Cloud Datastore Emulator 
> .
>
> You can opt-in to this feature by running:
> * dev_appserver.py --support_datastore_emulator*
>
> By using the --support_datastore_emulator flag, dev_appserver will use 
> Cloud Datastore Emulator for local datastore emulation. You can read more 
> about the migration process here 
> 
> .
> The development server and Cloud Datastore Emulator support the 
> interoperation of ndb and Cloud Datastore client libraries. 
>
> Please help us test this feature. Our goal is to enable it by default in 
> the future.
> Please share your feedback by replying directly to this thread. We are 
> looking forward to it!
>
> Thanks,
> Steren
> Product Manager
> Google Cloud
>

-- 
 


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/130045d9-755d-4a8f-b1c8-4a949641856f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.