[google-appengine] 如何验证自己的app应用？

[zhangshaofeng308]

对我来说我不得不允许不够安全的应用访问。是否可以通过验证自己的app来完善？
我申请app时并没有通过手机验证，补上这一步就可以了吗？如何补上这一步？ 

谢谢。I'm looking forward from you.

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cabcd7ef-2408-4e94-9517-1494cda36f1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google cloud endpoint error in production, no stack trace

[Aakash Bapna]

The log viewer in production does not show stack trace? Is there a setting 
somewhere to enable?

My google cloud endpoint works fine on local, but gives error on 
production. I am not getting any headway in debugging this.

Below is the error on production.

Request URL: https://mapp.appspot.com/_ah/api/myapi/v1/mymethod Method: 
myapi.mymethod *Error Code: 400 Reason: parseError Message: Parse Error*





-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/799690b4-aed4-4521-b9e0-a44dc3e4fd98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google App Engine Trial Version

[Barry Hunter]

For App Engine specifically there is a daily free quota
https://cloud.google.com/pricing/#app-engine

that is perpetual and lasts indefinitely (ie its not part of the 60 day
trail promotion)


I THINK you could use the trial credit, if you needed BEYOND what available
in the normal free quota)

On 6 March 2015 at 05:15,  wrote:

>  Hi Everybody
>
>
> I am new to Google Apps Engine , I plan to use the trial version
> for my project , the scope of my project is very small only and it will
> last about 6-9 month, can I know what is the effect if the trial version
> was expired because it 's only last 60 days. I have been go through the
> link below , can I know what is the meaning of  "All applications are
> free within a usage quota that is reset daily"? is it all the application
> is free as long as I am not overuse the quota even for the trial version
> https://cloud.google.com/pricing/
>
>
> thank you
>
> --
> 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 http://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/ab0c34d5-43c4-4b08-a9c3-fb79763da1a6%40googlegroups.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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJCAUu%2BGeW-WK9KzMJOwTD2oREms1zgCDpNk%3Dsq7u_A5cyb0Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Cannot create an app on app engine : Already exists error

[Rey Ncube]

I was using my email as an ID, its sorted now, I changed to a unique name
that i don't use on an Google account.

Thanks,

Rey

On Wed, Mar 4, 2015 at 6:58 PM, 'Josh Moyer' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Can you provide a list of the application IDs that you've tried and exact
> error messages?  Screenshots of the error (include the entire browser
> window, including the address bar) may be helpful, too.
>
> On Wed, Mar 4, 2015 at 3:25 AM, Rey Ncube  wrote:
>
>> Have tried a bunch of  application IDs but it doesn't work
>>
>> --
>> 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 http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-appengine/c7ca07b3-fc53-4c45-8c0d-e7db07c1242b%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Thanks,
> Josh
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/2W4g82iSFZk/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CAPdGywEbj1LmEW%2BY1d4yvgn97KW01FUJHrS%2BdM-Yz%3DuqN1%2BOEw%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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB2%2B0TCAR6DS6zG6cNejzFNswY%3DMShLzkDG1yDhVdtWFaLV1Mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "One senses GAE is just not a major priority for Google"

[DT Rush]

This thread is silly and bad

On Tuesday, October 28, 2014 at 5:11:15 PM UTC-4, Emanuele Ziglioli wrote:
>
> I would find hard to disagree:
>
> *IBM, Google, and Oracle are all equally at pains to deliver a message 
>> that makes them uniquely attractive. In this regard, Google's inability to 
>> recover from the botched roll-out of Google App Engine (GAE) will surely go 
>> down as one of the oddest business cases. It launched the product with 
>> great fanfare. But developers who flocked to it initially found a difficult 
>> platform that supported only a subset of Java and a very old version of 
>> Python. Moreover, the interfaces to the proprietary database were poorly 
>> thought out, so that almost everything in GAE required platform-specific 
>> code-arounds. While GAE has improved in a limited sense since then, Google 
>> has not done what Microsoft did — revamp the product from top to bottom to 
>> make it easy to use. Nor has it leveraged its natural connection to 
>> developers. One senses GAE is just not a major priority for Google.*
>
>
> http://www.drdobbs.com/cloud/whose-cloud-will-you-use/240169229
>
>
>

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b19df3ae-ef4b-436e-a38d-2ddd19b117be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "One senses GAE is just not a major priority for Google"

[DT Rush]

lol

I just have to say lol, at both the idea that code from within the last 5 
years is somehow legacy, and also that the developers console logs viewer 
is somehow not awesome. You know you can stream your logs to bigquery, you 
can put them in cloud storage, you can do all kinds of things, computer-y, 
programmer-y things to look at your logs, right? 


On Friday, November 7, 2014 at 11:17:35 PM UTC-5, Brandon Thomson wrote:
>
> Perhaps it is selfish on my part, but in some ways I am glad that GAE is 
> not getting much attention. Fixing bugs in legacy code is not exciting work 
> and a new generation of engineers at Google may be tempted to "improve" 
> things that aren't broken instead of doing the hard work of maintaining the 
> existing code.
>
> As an example of an unwanted "improvement," I would point to the new logs 
> viewer currently being advertised in the admin console. I don't like it at 
> all and I hope we will be able to keep using the existing logs viewer.
>

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8bc0082d-c2b8-4976-b0cf-660750a526bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Push to deploy discontinued?

[Dustin Hoffmann]

Hey Brad, my use case is this: I have a new html/css/js based single page 
app that I am hosting on Google Cloud. The old pipeline ui is now gone, and 
I am not a fan of Jenkins. All I want to do is have a simple deploy on git 
push like it was previously. Is this possible for me?
 

On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:
>
> Thanks for following up -- I am sorry this is confusing.   
>
> For Java developers, we recommend you use Jenkins as we describe here: 
> https://cloud.google.com/tools/repo/push-to-deploy
>
> does that help?
>
> ..brad
>
> On Wed, Mar 4, 2015 at 8:52 PM > 
> wrote:
>
>> Sorry I'm a bit confused as of how to exactly deploy a project.
>>
>> For existing projects I always used "git push origin master" to 
>> push-and-deploy. How would existing projects do that now? Will they 
>> continue to work? It seems as from yesterday this stopped working (but then 
>> I heard that it started working again...) It would be nice to know the 
>> official stance on this, if it *should* work or not.
>>
>> For new projects, we just have to use Jenkins, right? Or is there another 
>> way? That email, which we also received, stated that "gcloud app update" 
>> would work to deploy, but I don't think that's a working command at all. 
>> Please shed some light.
>>
>>
>>
>> On Tuesday, February 3, 2015 at 12:48:53 PM UTC+9, Brad Abrams wrote:
>>
>>>
>>> Thanks for all your feedback on this change. We heard from many of you 
>>> that, while the Jenkins-based solution we offer works 
>>> well for larger 
>>> projects with dedicated build and test steps, it works much less well for 
>>> more simple projects with no build or test steps.  
>>>
>>> To that end, we are going to continue to support push to deploy for 
>>> existing projects that don’t require build or test.  For example, python or 
>>> php applications code be pushed to the git repo and will be deployed to app 
>>> engine just as it works today.  We continue to recommend jenkins 
>>> for applications 
>>> that require build and test steps.
>>>
>>>
>>> If you have any problems with the source only deployments, please do let 
>>> me know. 
>>>
>>>
>>> Thanks again for your feedback.  
>>>
>>> ..brad
>>>
>>> On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi  
>>> wrote:
>>>
>> At the very least you should have a one liner notice when someone goes to 
 setup a new pipeline with deploy source only mentioning that it is 
 deprecated. We have a project that is still building as 'deploy source 
 only'... I made a new project and have spent days trying to figure out why 
 it doesn't deploy. I just happened to come across this thread in my 
 desperate attempts to figure out what is going on. I agree with Lucas that 
 "At least pushing source should remain as a feature". Having to do a lot 
 more to do exactly what we needed doesn't feel like an upgrade though I'm 
 sure some users will enjoy the extra capability.
  
 On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger wrote:
>
> Guys, this is absurd. You finally got the push-to-deploy product right 
> , and now you are discontinuing it. At least pushing source should remain 
> as a feature. 
> The whole appeal of push to deploy was NOT setting up Jenkins. I think 
> you are misjudging the number of people who object to using Jenkins. 
>  (By the way it was very disrespectful of you to cloak this 
> discontinuation as a feature upgrade. A tasteless and disingenuous 
> tactic, 
> to be precise.)

  -- 
 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-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
>>>
>>>
 Visit this group at http://groups.google.com/group/google-appengine.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-
 e3f1a4f4eb83%40googlegroups.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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/49a123fe-1398-42a3-b7d5-b4

Re: [google-appengine] Re: Push to deploy discontinued?

['Brad Abrams' via Google App Engine]

We really want to enable that use case.  The infrastructure we used for
that in the past has proven to not meet our reliability requirements, so we
are actively building a replacement.  As soon as that replacement is ready,
we will re-enable this functionality.

..brad



On Fri, Mar 6, 2015 at 9:18 AM Dustin Hoffmann 
wrote:

> Hey Brad, my use case is this: I have a new html/css/js based single page
> app that I am hosting on Google Cloud. The old pipeline ui is now gone, and
> I am not a fan of Jenkins. All I want to do is have a simple deploy on git
> push like it was previously. Is this possible for me?
>
>
> On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:
>
>> Thanks for following up -- I am sorry this is confusing.
>>
>> For Java developers, we recommend you use Jenkins as we describe here:
>> https://cloud.google.com/tools/repo/push-to-deploy
>>
>> does that help?
>>
>> ..brad
>>
>> On Wed, Mar 4, 2015 at 8:52 PM  wrote:
>>
> Sorry I'm a bit confused as of how to exactly deploy a project.
>>>
>>> For existing projects I always used "git push origin master" to
>>> push-and-deploy. How would existing projects do that now? Will they
>>> continue to work? It seems as from yesterday this stopped working (but then
>>> I heard that it started working again...) It would be nice to know the
>>> official stance on this, if it *should* work or not.
>>>
>>> For new projects, we just have to use Jenkins, right? Or is there
>>> another way? That email, which we also received, stated that "gcloud app
>>> update" would work to deploy, but I don't think that's a working command at
>>> all. Please shed some light.
>>>
>>>
>>>
>>> On Tuesday, February 3, 2015 at 12:48:53 PM UTC+9, Brad Abrams wrote:
>>>

 Thanks for all your feedback on this change. We heard from many of you
 that, while the Jenkins-based solution we offer works
 well for larger
 projects with dedicated build and test steps, it works much less well for
 more simple projects with no build or test steps.

 To that end, we are going to continue to support push to deploy for
 existing projects that don’t require build or test.  For example, python or
 php applications code be pushed to the git repo and will be deployed to app
 engine just as it works today.  We continue to recommend jenkins
 for applications
 that require build and test steps.


 If you have any problems with the source only deployments, please do
 let me know.


 Thanks again for your feedback.

 ..brad

 On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi 
 wrote:

>>> At the very least you should have a one liner notice when someone goes
> to setup a new pipeline with deploy source only mentioning that it is
> deprecated. We have a project that is still building as 'deploy source
> only'... I made a new project and have spent days trying to figure out why
> it doesn't deploy. I just happened to come across this thread in my
> desperate attempts to figure out what is going on. I agree with Lucas that
> "At least pushing source should remain as a feature". Having to do a lot
> more to do exactly what we needed doesn't feel like an upgrade though I'm
> sure some users will enjoy the extra capability.
>
> On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger wrote:
>>
>> Guys, this is absurd. You finally got the push-to-deploy product
>> right , and now you are discontinuing it. At least pushing source should
>> remain as a feature.
>> The whole appeal of push to deploy was NOT setting up Jenkins. I
>> think you are misjudging the number of people who object to using 
>> Jenkins.
>>  (By the way it was very disrespectful of you to cloak this
>> discontinuation as a feature upgrade. A tasteless and disingenuous 
>> tactic,
>> to be precise.)
>
>  --
> 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-appengi...@googlegroups.com.
> To post to this group, send email to google-a...@googlegroups.com.


> Visit this group at http://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-e3f1a4f4eb83%
> 40googlegroups.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 unsubsc

Re: [google-appengine] Re: Push to deploy discontinued?

[Dustin Hoffmann]

Thanks Brad, really looking forward to having that back in business!

On Friday, March 6, 2015 at 11:23:28 AM UTC-6, Brad Abrams wrote:
>
> We really want to enable that use case.  The infrastructure we used for 
> that in the past has proven to not meet our reliability requirements, so we 
> are actively building a replacement.  As soon as that replacement is ready, 
> we will re-enable this functionality.
>
> ..brad
>
>
>
> On Fri, Mar 6, 2015 at 9:18 AM Dustin Hoffmann  > wrote:
>
>> Hey Brad, my use case is this: I have a new html/css/js based single page 
>> app that I am hosting on Google Cloud. The old pipeline ui is now gone, and 
>> I am not a fan of Jenkins. All I want to do is have a simple deploy on git 
>> push like it was previously. Is this possible for me?
>>  
>>
>> On Wednesday, March 4, 2015 at 11:02:03 PM UTC-6, Brad Abrams wrote:
>>
>>> Thanks for following up -- I am sorry this is confusing.   
>>>
>>> For Java developers, we recommend you use Jenkins as we describe here: 
>>> https://cloud.google.com/tools/repo/push-to-deploy
>>>
>>> does that help?
>>>
>>> ..brad
>>>
>>> On Wed, Mar 4, 2015 at 8:52 PM  wrote:
>>>
>> Sorry I'm a bit confused as of how to exactly deploy a project.

 For existing projects I always used "git push origin master" to 
 push-and-deploy. How would existing projects do that now? Will they 
 continue to work? It seems as from yesterday this stopped working (but 
 then 
 I heard that it started working again...) It would be nice to know the 
 official stance on this, if it *should* work or not.

 For new projects, we just have to use Jenkins, right? Or is there 
 another way? That email, which we also received, stated that "gcloud app 
 update" would work to deploy, but I don't think that's a working command 
 at 
 all. Please shed some light.



 On Tuesday, February 3, 2015 at 12:48:53 PM UTC+9, Brad Abrams wrote:

>
> Thanks for all your feedback on this change. We heard from many of you 
> that, while the Jenkins-based solution we offer works 
> well for larger 
> projects with dedicated build and test steps, it works much less well for 
> more simple projects with no build or test steps.  
>
> To that end, we are going to continue to support push to deploy for 
> existing projects that don’t require build or test.  For example, python 
> or 
> php applications code be pushed to the git repo and will be deployed to 
> app 
> engine just as it works today.  We continue to recommend jenkins 
> for applications 
> that require build and test steps.
>
>
> If you have any problems with the source only deployments, please do 
> let me know. 
>
>
> Thanks again for your feedback.  
>
> ..brad
>
> On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi  
> wrote:
>
 At the very least you should have a one liner notice when someone goes 
>> to setup a new pipeline with deploy source only mentioning that it is 
>> deprecated. We have a project that is still building as 'deploy source 
>> only'... I made a new project and have spent days trying to figure out 
>> why 
>> it doesn't deploy. I just happened to come across this thread in my 
>> desperate attempts to figure out what is going on. I agree with Lucas 
>> that 
>> "At least pushing source should remain as a feature". Having to do a lot 
>> more to do exactly what we needed doesn't feel like an upgrade though 
>> I'm 
>> sure some users will enjoy the extra capability.
>>  
>> On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger wrote:
>>>
>>> Guys, this is absurd. You finally got the push-to-deploy product 
>>> right , and now you are discontinuing it. At least pushing source 
>>> should 
>>> remain as a feature. 
>>> The whole appeal of push to deploy was NOT setting up Jenkins. I 
>>> think you are misjudging the number of people who object to using 
>>> Jenkins. 
>>>  (By the way it was very disrespectful of you to cloak this 
>>> discontinuation as a feature upgrade. A tasteless and disingenuous 
>>> tactic, 
>>> to be precise.)
>>
>>  -- 
>> 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-appengi...@googlegroups.com.
>> To post to this group, send email to google-a...@googlegroups.com.
>
>
>> Visit this group at http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-e3f1a4f4eb83%
>> 40googlegrou

[google-appengine] Re: Google cloud endpoint error in production, no stack trace

[Chad Vincent]

Are you logging the exception?  What language?

I don't know what you're using, but the uncaught exception handler in Java 
does log the stack trace.


On Friday, March 6, 2015 at 5:15:29 AM UTC-6, Aakash Bapna wrote:
>
> The log viewer in production does not show stack trace? Is there a setting 
> somewhere to enable?
>
> My google cloud endpoint works fine on local, but gives error on 
> production. I am not getting any headway in debugging this.
>
> Below is the error on production.
>
> Request URL: https://mapp.appspot.com/_ah/api/myapi/v1/mymethod Method: 
> myapi.mymethod *Error Code: 400 Reason: parseError Message: Parse Error*
>
>
>
>
>
>

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a674c001-0e75-434b-a5c1-ab748b8deab3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"

[Brandon Thomson]

Yup, golang is the winner. Perfect fit for GAE's architecture, URL routing 
included in stdlib... love it.

On Friday, February 27, 2015 at 3:04:44 AM UTC-5, Tapir wrote:
>
> you will find it really difficult to implement oauth, sessions, rest, 
>> rbac, etc... 
>> Webapp2 it's completely abandoned! And given that almost all app engine 
>> examples on python rely on webapp2... that's a big flaw.
>>
>
> just try golang, that is all.
>
> Java is slow to startup and very memory consuming and slow for development.
> PHP and Python is slow on performance.
> Golang is both fast for development and fast to startup and fast on 
> performance, and it is maintained actively.
>

-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0cc47457-f92f-4799-9b3e-35d0e9c796c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google cloud endpoint error in production, no stack trace

[Aakash Bapna]

It's Python, I think the exception is thrown in google cloud endpoint lib. 

-
Aakash

> On 07-Mar-2015, at 2:11 am, Chad Vincent  wrote:
> 
> Are you logging the exception?  What language?
> 
> I don't know what you're using, but the uncaught exception handler in Java 
> does log the stack trace.
> 
> 
>> On Friday, March 6, 2015 at 5:15:29 AM UTC-6, Aakash Bapna wrote:
>> The log viewer in production does not show stack trace? Is there a setting 
>> somewhere to enable?
>> 
>> My google cloud endpoint works fine on local, but gives error on production. 
>> I am not getting any headway in debugging this.
>> 
>> Below is the error on production.
>> 
>> Request URL: https://mapp.appspot.com/_ah/api/myapi/v1/mymethod
>> Method: myapi.mymethod
>> Error Code: 400
>> Reason: parseError
>> Message: Parse Error
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Google App Engine" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/google-appengine/tUls2TByhlM/unsubscribe.
> To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-appengine.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/a674c001-0e75-434b-a5c1-ab748b8deab3%40googlegroups.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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1EC2DBD8-E68A-41CF-A9B4-AE3D181D8632%40gmail.com.
For more options, visit https://groups.google.com/d/optout.