[google-appengine] Re: dev_appserver hangs while running tests

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Shaunak,

Interesting indeed! My SDK version is: 

$ goapp version
go version 1.6.3 (appengine-1.9.53) linux/amd64

Downgrading to 1.9.48 didn't cause the issue to appear, either. I'm running 
an Intel(R) Xeon(R) CPU @ 2.2 GHz, and I only have 7.3G memory!

I'm running the exact code you'd specified above, as well... Is it possible 
that your CPU and memory are being quite used-up by other processes?

Cheers,

Nick
Cloud Platform Community Support

On Thursday, May 11, 2017 at 6:45:20 PM UTC-4, Shaunak Godbole wrote:
>
> That's interesting.
>
> goapp version prints the following:
>
> go version go1.6.3 (appengine-1.9.48) darwin/amd64
>
>
>
> I'm using MacBookPro with the following configuration:
> Processor: 2.2 GHz Intel Core i7 
> Memory 16G
> Graphics Intel Iris Pro 1536MB
>
> Thanks!
> Shaunak
>
>
> On Thursday, May 11, 2017 at 3:19:06 PM UTC-7, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Shaunak,
>>
>> I've not been able to observe the crash as you saw. For me, it completes 
>> in a timely manner. I'm curious to know what version of the SDK you're 
>> using now and what are the specs of the machine you're running this on?
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, May 11, 2017 at 10:32:50 AM UTC-4, Shaunak Godbole wrote:
>>>
>>> Thanks Nick, 
>>>
>>> I was able to isolate the problem significantly.  It seems like there is 
>>> a limit on the number of operations that can be read in a given amount of 
>>> time.  If you run the following program:
>>>
>>> package main
>>>
>>> import (
>>> "fmt"
>>> "testing"
>>>
>>> "google.golang.org/appengine"
>>> "google.golang.org/appengine/aetest"
>>> "google.golang.org/appengine/datastore"
>>> )
>>>
>>> type Entity struct {
>>>   Id int64
>>> }
>>>
>>> func TestLoad(t *testing.T) {
>>> opts := aetest.Options{StronglyConsistentDatastore: true}
>>> inst, _ := aetest.NewInstance(opts)
>>> defer inst.Close()
>>>
>>>
>>> for i := 0; i < 1; i++ {
>>> req, _ := inst.NewRequest("GET", "/", nil)
>>> ctx := appengine.NewContext(req)
>>>
>>> k := datastore.NewKey(ctx, "Entity", "", 12345, nil)
>>> var entity Entity
>>> datastore.Get(ctx, k, )
>>> fmt.Println("Iteration Count ", i+1)
>>> ctx.Done()
>>> }
>>> }
>>>
>>> This program gets stuck at Iteration count 240.  We suspect that aetest, 
>>> or appengine go library releases its hold on some resources only after 
>>> ctx.deadline expires.  This code seems to pass through if we change the 
>>> context deadline to be 50 ms.  Increasing the deadline still makes the 
>>> program pass through but after 240th iteration, we see each subsequent step 
>>> taking roughly the same time as deadline.
>>>
>>> We also added code to see the number of goroutines that get added as 
>>> part of the each of the steps and can see that 2 goroutines are added at 
>>> every step and the number keeps on increasing until step number 240.  Our 
>>> guess is that these goroutines are holding up the resources.  Is there any 
>>> way to determine which goroutines are these?
>>>
>>> Thanks,
>>> Shaunak
>>>
>>>
>>> On Wednesday, May 10, 2017 at 1:13:04 PM UTC-7, Nick (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> Hey Shaunak,
>>>>
>>>> You might want to run a set of tests across the parameter space of all 
>>>> the relevant variables:
>>>>
>>>> Vary the total number of tests:
>>>>
>>>> N = number of tests total
>>>>
>>>>
>>>> Vary the proportion of N taken up by each type of test:
>>>>
>>>> N_a = number of tests of type a
>>>> N_b = number of tests of type b
>>>>
>>>> . . . 
>>>>
>>>> N_e = number of tests of type e
>>>>
>>>> . . . 
>>>>
>>>>
>>>> Vary the parameters of the tests themselves:
>>>>
>>>> a_x = critical parameter x involved in running a test of type a
>>>> a_y = critical parameter y involved in running a test of type a
>>>> . . .
>>>> e_x = critical parameter x involved in run

[google-appengine] Re: dev_appserver hangs while running tests

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Shaunak,

I've not been able to observe the crash as you saw. For me, it completes in 
a timely manner. I'm curious to know what version of the SDK you're using 
now and what are the specs of the machine you're running this on?

Cheers,

Nick
Cloud Platform Community Support

On Thursday, May 11, 2017 at 10:32:50 AM UTC-4, Shaunak Godbole wrote:
>
> Thanks Nick, 
>
> I was able to isolate the problem significantly.  It seems like there is a 
> limit on the number of operations that can be read in a given amount of 
> time.  If you run the following program:
>
> package main
>
> import (
> "fmt"
> "testing"
>
> "google.golang.org/appengine"
> "google.golang.org/appengine/aetest"
> "google.golang.org/appengine/datastore"
> )
>
> type Entity struct {
>   Id int64
> }
>
> func TestLoad(t *testing.T) {
> opts := aetest.Options{StronglyConsistentDatastore: true}
> inst, _ := aetest.NewInstance(opts)
> defer inst.Close()
>
>
> for i := 0; i < 1; i++ {
> req, _ := inst.NewRequest("GET", "/", nil)
> ctx := appengine.NewContext(req)
>
> k := datastore.NewKey(ctx, "Entity", "", 12345, nil)
> var entity Entity
> datastore.Get(ctx, k, )
> fmt.Println("Iteration Count ", i+1)
> ctx.Done()
> }
> }
>
> This program gets stuck at Iteration count 240.  We suspect that aetest, 
> or appengine go library releases its hold on some resources only after 
> ctx.deadline expires.  This code seems to pass through if we change the 
> context deadline to be 50 ms.  Increasing the deadline still makes the 
> program pass through but after 240th iteration, we see each subsequent step 
> taking roughly the same time as deadline.
>
> We also added code to see the number of goroutines that get added as part 
> of the each of the steps and can see that 2 goroutines are added at every 
> step and the number keeps on increasing until step number 240.  Our guess 
> is that these goroutines are holding up the resources.  Is there any way to 
> determine which goroutines are these?
>
> Thanks,
> Shaunak
>
>
> On Wednesday, May 10, 2017 at 1:13:04 PM UTC-7, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Shaunak,
>>
>> You might want to run a set of tests across the parameter space of all 
>> the relevant variables:
>>
>> Vary the total number of tests:
>>
>> N = number of tests total
>>
>>
>> Vary the proportion of N taken up by each type of test:
>>
>> N_a = number of tests of type a
>> N_b = number of tests of type b
>>
>> . . . 
>>
>> N_e = number of tests of type e
>>
>> . . . 
>>
>>
>> Vary the parameters of the tests themselves:
>>
>> a_x = critical parameter x involved in running a test of type a
>> a_y = critical parameter y involved in running a test of type a
>> . . .
>> e_x = critical parameter x involved in running a test of type e
>>
>> . . . 
>>
>>
>> You would script a series of runs of test suites defined by their 
>> position in "test suite parameter space" (N, N_a, N_b, . . . , N_e, . . . , 
>> a_x, a_y, . . . ,  e_x, . . .), programmatically logging whether the test 
>> suite completed or crashed, how long it took before it crashed if so, and 
>> you could possibly observe correlations between crashing and certain kinds 
>> of tests and/or rule out which variables seem to have no impact on whether 
>> it crashes or not.
>>
>> * * *
>>
>> Beyond that, though, it seems you'd need to either go source-code diving 
>> or get the assistance of someone who actually works on the codebase of the 
>> go SDK and aetest. You might want to file an issue in the github issue 
>> tracker for aetest <https://github.com/golang/appengine> as soon as you 
>> can get more info from a more rigorous test of test suite parameters as 
>> described above.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>>
>> On Wednesday, May 10, 2017 at 1:07:39 PM UTC-4, Shaunak Godbole wrote:
>>>
>>> Hello, we are using aetest to write some integration tests as part of 
>>> our project.  The integration tests spin up an instance of a 
>>> dev_appserver.py in a *BeforeSuite* function.  We use APIs to guarantee 
>>> that the suite executes before we start the test:
>>>
>>> func BeforeSuite() {
>>>   params := aetest.InstanceParams{StrongConsistency: true}
>>>   inst := aetest.NewInstance(params)
>>>   req := 

[google-appengine] Re: dev_appserver hangs while running tests

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Shaunak,

You might want to run a set of tests across the parameter space of all the 
relevant variables:

Vary the total number of tests:

N = number of tests total


Vary the proportion of N taken up by each type of test:

N_a = number of tests of type a
N_b = number of tests of type b

. . . 

N_e = number of tests of type e

. . . 


Vary the parameters of the tests themselves:

a_x = critical parameter x involved in running a test of type a
a_y = critical parameter y involved in running a test of type a
. . .
e_x = critical parameter x involved in running a test of type e

. . . 


You would script a series of runs of test suites defined by their position 
in "test suite parameter space" (N, N_a, N_b, . . . , N_e, . . . , a_x, 
a_y, . . . ,  e_x, . . .), programmatically logging whether the test suite 
completed or crashed, how long it took before it crashed if so, and you 
could possibly observe correlations between crashing and certain kinds of 
tests and/or rule out which variables seem to have no impact on whether it 
crashes or not.

* * *

Beyond that, though, it seems you'd need to either go source-code diving or 
get the assistance of someone who actually works on the codebase of the go 
SDK and aetest. You might want to file an issue in the github issue tracker 
for aetest  as soon as you can get 
more info from a more rigorous test of test suite parameters as described 
above.

Cheers,

Nick
Cloud Platform Community Support


On Wednesday, May 10, 2017 at 1:07:39 PM UTC-4, Shaunak Godbole wrote:
>
> Hello, we are using aetest to write some integration tests as part of our 
> project.  The integration tests spin up an instance of a dev_appserver.py 
> in a *BeforeSuite* function.  We use APIs to guarantee that the suite 
> executes before we start the test:
>
> func BeforeSuite() {
>   params := aetest.InstanceParams{StrongConsistency: true}
>   inst := aetest.NewInstance(params)
>   req := aetest.NewRequest("Get", "/", nil)
>   ctx := appengine.NewContext(req)
> }
>
> We have a similar *AfterSuite* that tears down the instance. 
>
> func AfterSuite() {
>   inst.Close()
> }
>
> Since we want the tests to be completely hermetic, we delete all the 
> entities that we had created during the tests, usually in an *AfterEach* 
> method.
>
> func AfterEach() {
>   deleteAllEntitiesFromDatastore("ENTITY_1")
>   deleteAllEntitiesFromDatastore("ENTITY_2")
>   deleteAllEntitiesFromDatastore("ENTITY_3")
>   ...
> }
>
> And, the we have a lot of test cases that simply run against the created 
> instance and use the context acquired through *BeforeSuite*.  We have a 
> good mixture of Gets, Puts, Entity Queries, Filter Queries etc.  Since a 
> few days, every-time we run our tests, the tests hang at some point during 
> the execution.  This point changes as we add and remove some of the tests, 
> but the tests always hang if the number of suites are above a certain 
> threshold.  We usually see errors like:
>
> : Call error 11: Deadline exceeded (timeout)
>
>
> or like:
>
> Expected success, but got an error:
> <*url.Error | 0xc8210570b0>: {
> Op: "Post",
> URL: "http://localhost:59072;,
> Err: {s: "EOF"},
> }
> Post http://localhost:59072: EOF
>
>
> While the tests are hung, if we try to access the datastore through the ip 
> produced in the tests, the request just hangs similar to how it hangs 
> during the tests.  This makes us suspicious that there is some kind of a 
> deadlock that is getting introduced during our execution, but we are not 
> able to figure out how to debug it.  
>
> Also, the test suites have a timeout after which the tests simply crash. 
>  At this point, the AfterSuite cannot execute so the test-server remains 
> active in the background, and when we try to access datastore through the 
> admin, we can see all the data that was added as part of the test.
>
> For completeness sake, we also use gomocks to abstract out some external 
> services as part of the tests.
>
> Any help on debugging this would be very much appreciated.
>
> Thanks,
> Shaunak
>

-- 
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/96fd7d98-d4c9-4631-ae45-0b7318863818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: google-plus phising via plus.sfghfghfdg.appspot.com

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Jerry,

It appears the app sfghfghfdg is spoofing the google.com search page. This 
could indeed be part of a phishing attempt by the creator of the app. We've 
taken note of this and will review the app.

However, as for the "insecure page", this is a result of the fact that the 
appspot.com domain does not serve a certificate which covers 
*.*.appspot.com, which is the format of the domain 
plus.sfghfghfdg.appspot.com. The page you see is a standard page served by 
your browser to warn the user of this fact. 

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, May 10, 2017 at 1:08:46 PM UTC-4, Jerry Hopper wrote:
>
>
> Via google search, a strange result popped up:
>
> https://plus.sfghfghfdg.appspot.com/+  which leads to a 
> insecure page. (attempt to steal credentials?)
>
> http://plus.sfghfghfdg.appspot.com/  <--- ends up on some advertising page
>
>
>

-- 
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/49cf38b8-8b1f-4de2-80df-8be5c19e9de1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: billing account closed?

['Nick (Cloud Platform Support)' via Google App Engine]

You'll need to contact billing 
 about 
this. Unfortunately I can't tell you why this might be occurring.

Best of luck!

Nick
Cloud Platform Community Support

On Wednesday, May 10, 2017 at 1:08:57 PM UTC-4, stjin...@gmail.com wrote:
>
> well, i'm trying to create my first project, but it says my billing 
> account got closed, why is this?
> i asked my bank and they told me everything was fine on their side. am i 
> doing something wrong?
> if i try to re-add the billing account i get this error
>
> "Unexpected error, try again later"
>
> can someone help me with this issue please
>

-- 
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/ddb4b973-43f6-450d-9f17-2f548e28e8ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine Flex "Error: Server Error" occurs often, how to find cause?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Alon,

>From what I can see online, it seems that error comes from collectd, a 
logging service running on the instance. Can you try to run the docker 
container for your app locally and see what happens? Here are the steps:

1. *Generate* the *Dockerfile* if you don't already have one:

 

gcloud beta app gen-config 
<https://cloud.google.com/sdk/gcloud/reference/beta/app/gen-config> --custom


2. *Build* a *docker image* from the Dockerfile:


docker build <https://docs.docker.com/engine/reference/commandline/build/> 
-t myappcontainer .


3. *Run* a *docker container* using the docker image


 docker run <https://docs.docker.com/engine/reference/run/> -p 
127.0.0.1:8080:8080 myappcontainer


You can then observe the container starting up, or see if there's an error 
when you send a request to 8080 (note that 8080 is the port most apps 
listen on, but you might need to use another port if your app (such as the 
sanic <https://github.com/channelcat/sanic> framework, for example, which 
uses 8000) doesn't use 8080).

Let me know how it goes,

Cheers,

Nick
Cloud Platform Community Support


On Wednesday, May 10, 2017 at 1:06:51 PM UTC-4, Alon Schwartzman wrote:
>
> Hi Nick.
>
> I just deployed a node js app and I'm experiencing the same issue.
>
> Usingt the Stackdriver logs i can see the instance fails to start my app.
>
> read-function of plugin `tail-0' failed. Will suspend it for 480.000 
> seconds."   
>
> Can you help?
>
> Thanks 
>
>
>
>
>
> On Friday, March 3, 2017 at 5:40:17 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Nickolas,
>>
>> This forum should be used to post general discussion threads about the 
>> platform, services, design patterns, etc., and a specific-issue question 
>> like this should be posted to Stack Overflow, although maybe we could 
>> gather more information before that, as in this state it seems there's not 
>> quite enough information for anyone to begin working on it. I have some 
>> lines of investigation which might lead to a better understanding:
>>
>> 1 .This could be a case of not inspecting the logs with the right logs 
>> level - are you sure you're viewing "All logs", and not just "stdout, 
>> stderr"? 
>>
>>
>> <https://lh3.googleusercontent.com/-QzbBJlxqcmg/WLmNadNzaFI/DMo/HE_w_IDDO6czwSeBhDzxj48VQ4cAPBc2wCLcB/s1600/Screenshot%2B2017-03-03%2Bat%2B10.35.59%2BAM.png>
>>
>> 2. You might also want to check whether you have any logs for the 
>> resource "Cloud HTTP Load Balancer" as opposed to "GAE Application" 
>>
>> 3. A final thing to check would be the headers attached to the response - 
>> specifically looking to see what the "server" header says - to determine 
>> whether this response is generated by our machines or your own. It seems to 
>> look like an error that our infrastructure generates, not your app, but 
>> it's good to check.
>>
>> Let me know what you find, and feel free to ask any further questions or 
>> provide any information you think may be relevant.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, March 2, 2017 at 7:19:16 PM UTC-5, Nickolas Daskalou wrote:
>>>
>>> Hi,
>>>
>>> If we hit our Flexible environment service (Python 3 runtime) with a 
>>> relatively low concurrency level using ApacheBench, we get this returned 
>>> more often than not:
>>>
>>> Error: Server ErrorThe server encountered a temporary error and could 
>>> not complete your request.
>>>
>>> Please try again in 30 seconds.
>>>
>>> I can't seem to find any information in any of logs about why this is 
>>> occurring.
>>>
>>> Is there a way to get the cause of the above page being returned, 
>>> whether it be via the logs or otherwise?
>>>
>>> Thanks,
>>> Nick
>>>
>>

-- 
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/92a6c7de-cc5d-4dcc-8d3a-4d2590515ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cron.xml not picked up - where do I start looking?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Torbjørn, 

Which app engine maven plugin are you using? Could you post the section 
from your pom.xml? Does it look like the documentation? 


Cheers,

Nick
Cloud Platform Community Support

On Saturday, May 6, 2017 at 2:55:33 PM UTC-4, Torbjørn Smørgrav wrote:
>
> Thanks Nick,
>
> I'll stick to Stack Overflow for these questions going forward.
>
> My maven plugin version did not have the deployCron goal. But I learned 
> just now that I would have to(?) use appcfg.sh update or updatecron to do 
> this.
>
> Cheers,
> -T
>
>
>

-- 
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/e38ddd5b-210d-4b4c-bcd6-8e5d1d4a83a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey E,

I've seen it before where the app is actually serving but it takes some 
time for the deployment *command *to complete. In the operation info, it 
says, "servingStatus: SERVING". Could you check, when this occurs, whether 
the app isn't serving *before *the command ends? 
Cheers,

Nick
Cloud Platform Community Support

On Thursday, May 4, 2017 at 4:03:08 PM UTC-4, E EE wrote:
>
> From the logs it seems like the operation is the deployment of a new 
> version. See attached dump of the command.
>

-- 
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/baebc850-a434-4b3f-b17f-3e03d610fe39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cron.xml not picked up - where do I start looking?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Torbjørn,

While cron.xml may have been part of the deployed application folder, that 
doesn't mean that you've run the command to deploy the cron settings. Could 
you try to run 

mvn appengine:deployCron


And report back the results?

I'll just note here while I can, that in general this forum is not meant 
for specific-issue technical support. You should post to Stack Overflow 
 with questions like these, as we monitor our 
tags there and there is also a much larger user-base able to support your 
question.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, May 2, 2017 at 3:36:05 PM UTC-4, Torbjørn Smørgrav wrote:
>
> I'm trying to get cron jobs working.
>
>
> The /status url that I want to hit in the cron job is configured and 
> working. From web.xml:
>
>
> 
> StatusServlet
> my.package.StatusServlet
> 
> 
> StatusServlet
> /status
> 
>
>
> From the debugger you can see that cron.xml is uploaded:
>
>
>
> 
>
> But I don't see anything in the logs... the servlet is never called.
>
> What am I missing?
>
>
>
>

-- 
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/36ab10bf-2328-45b5-bebb-ad1b2fe5a2a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey E,

Alright, now given that I can't look into what operation that is, you 
should check what it is using gcloud, using the command below:

gcloud beta app operations describe d8c581c51b0-e9a02f


Possibly it's the same issue discussed above, the creation of the load 
balancer.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, May 3, 2017 at 5:27:24 PM UTC-4, E EE wrote:
>
> Here is the log file from cloud shell
>
> You can see many:
> Operation [apps/my-project/operations/d8c581c51b0-e9a02f] not complete. 
> Waiting 5s.
>

-- 
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/a0038e58-7108-4cc9-a541-7f00ce5a7436%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey E,

The log file location is given when you run the gcloud info command. In 
your case, the output showed:

Logs Directory: [/tmp/tmp.ijTCcTysEa/logs]
Last Log File: [None]


It's odd that there should be "None" for the last log file. Did you run the 
failing command before running gcloud info? And are there any log files in 
/tmp/tmp.ijTCcTysEa/logs? It's possible with a file path like that that the log 
directory is temporary, so the logs from a prior deployment may not be saved 
unless you actively retrieve them after the fact within a given timeframe.

Cheers,

Nick
Cloud Platform Community Support


On Tuesday, May 2, 2017 at 4:59:05 PM UTC-4, E EE wrote:
>
> The latest attempt to deploy from the browser console resulted in:
>
> ERROR: (gcloud.app.deploy) Error Response: [13] Unexpected Error. (The 
> API call stubby.Send() took too long to respond and was cancelled.)
>
> Attached the log, nothing jumps out there.
>

-- 
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/0c7b233f-f904-43bb-be68-9151c60b7213%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Добрый день! Кто может помочь по Compute Engine? Есть пару вопросов

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Николай,

I translated your message to english and I think you were asking whether 
you would still be charged for your Compute Engine machines whether they 
are "working" or not. If they aren't running, you won't be charged, but if 
they are running, even if your web app isn't serving, or they aren't doing 
whatever you want them to do - you will still be charged. I hope that helps 
clarify the situation. You can read more in the documentation 
.

Cheers,

Nick
Cloud Platform Community Support

On Monday, May 1, 2017 at 9:07:27 AM UTC-4, Николай Кармазин wrote:
>
> Заранее спасибо за ответы. Если я создам машину. Деньги буду сниматься 
> независимо от того, работает машина или нет? 
>

-- 
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/e1aebbb0-30d1-4439-a181-520f2bf07e94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Mystic! Browser behavior

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Денис,

This forum is meant for discussion of the platform and not for technical 
support. You should post to Stack Overflow  with 
a more clear explanation of your issue and the users there will be happy to 
assist you. We monitor our tags on Stack Overflow as well. I'd suggest 
mentioning:

1. What you expect to see
2. What you see instead
3. Details about how you've written / configured your app


Cheers,

Nick
Cloud Platform Community Support

On Monday, May 1, 2017 at 5:28:43 PM UTC-4, Денис Волконский wrote:
>
>
> 
> I deploy angular 2 site on google app engine, it show me problem with my 
> backend. Then I update its project my old version on angularjs only whith 
> static folder except dist folder, and different appyaml. So then I see this 
> - in Chrome angular 2 version and on mobile and mozila - angularjs!!! 
> And  in Chrome angular 2 version START WORKING!!! WHY???
>

-- 
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/d3c16a98-56d5-4797-b502-570bb430d141%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey E,

You should analyze (or sanitize and then attach here) the logs produced by 
the deployment. You can find the logs location by running 'gcloud info'.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, May 2, 2017 at 3:11:12 PM UTC-4, E EE wrote:
>
> I am having the same problem in region US central and a hello world Java 
> app (app engine flexible). This is a tiny app with one servlet that prints 
> hello, it does not get smaller than that.
>
> It happens from both my local machine as well as the browser console, 
> using both gradle as well as "gcloud app deploy" command.
>

-- 
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/2df1cc13-d1a0-4934-ba70-e71e22bc34e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Maven error on app-engine 1.9.22

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Sahil,

You should open a Q on Stack Overflow  
explaining what you're doing, without reference to any other person's post, 
and people will be able to help you from that point. We monitor our tags on 
Stack Overflow and I'll be happy to assist if you post the link to your 
Stack Overflow Q here once it's made.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, April 25, 2017 at 11:01:19 AM UTC-4, sahil nagpal wrote:
>
>
> It is not resolved for my side , Tim - please help
>

-- 
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/c0595f48-9eb8-40fc-9358-2babac0c2625%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppIdentity Credential vs Application Default Credentials

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Nicola,

There's no comparison chart, but your post itself has correctly discerned 
the major differences. AppIdentity is used to assert the identity of the 
application in production, and uses the default App Engine service account. 
Application Default Credentials in a deployed App Engine app will also use 
this same identity, however (as you noticed), in dev, Application Default 
Credentials will use the gcloud credentials.

Regards,

Nick
Cloud Platform Community Support

On Friday, April 28, 2017 at 8:41:07 AM UTC-4, Nicola Spreafico wrote:
>
> Hi,
> I'm unable to properly understand the differences between this 2 
> authentication methods:
>
> AppIdentity: 
> https://cloud.google.com/appengine/docs/standard/java/appidentity/#asserting_identity_to_google_apis
> Application Default Credentials: 
> https://developers.google.com/identity/protocols/application-default-credentials#whentouse
>
> My use case is use the Google APIs with the App Engine application itself 
> as authenticated user.
>
> As far I can understand, with Application Default Credentials I can create 
> an "hybrid" code that can work in both local and online environment (in 
> local the user will be my own, configured in GCloud, and online will be the 
> application).
> The AppIdentity method instead does not work in local enviroment.
>
> The AppIdentify only provides and accessToken (but a Credential object can 
> be built using this token)
> The ApplicationDefaultCredentials directly provides a Credential object
>
> is there a comparison chart available?
>

-- 
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/9abbfbfb-516a-4c30-92dc-44edfc3d7215%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Temporary storage of data bigger than 1 Mega

['Nick (Cloud Platform Support)' via Google App Engine]

While using the Flexible Environment or a dedicated Compute Engine instance 
would probably be the simplest solution, you may also consider (if 
committed to using the Standard Environment of App Engine) breaking up the 
file into several pieces are storing these in Memcache, maintaining their 
freshness as necessary (changes to the underlying model, a given file part 
being evicted from the cache).

Cheers,

Nick
Cloud Platform Community Support 

On Monday, April 24, 2017 at 5:16:18 PM UTC-4, Shachar Grembek wrote:
>
> Thanks for the suggestion, but as you mentioned, it would be too extreme 
> to redesign the architecture, just because of that
>
> On Monday, April 24, 2017 at 6:53:24 PM UTC+3, Justin Beckwith wrote:
>>
>> While I'm sure there are other options you should explore first, one idea 
>> is to look at using App Engine Flexible.  The instances in flex tend to 
>> last longer [o(days)], and the data could be cached on the instance.  
>>
>> Depending on the APIs and services you're using, a change like this could 
>> be pretty extreme, so you may want to read up on the differences here:
>> https://cloud.google.com/appengine/docs/the-appengine-environments
>>
>>
>>
>> On Mon, Apr 24, 2017 at 8:25 AM, Shachar Grembek  
>> wrote:
>>
>>> Hi,
>>>
>>> I have a resource file that its size is 1.6 Mega (A Machine learning 
>>> model). The data is required and needs to be loaded for every API call I 
>>> receive, but loading the file to memory takes around 8 seconds. So I would 
>>> like to find a way to have the data available in a more efficient manner. I 
>>> considered to store the data in Memcache, but Memcache objects are limited 
>>> to 1M. I would really appreciate, if someone can help me find a way to 
>>> store it in a manner so it can be loaded it in 1 second or less.
>>>
>>> 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-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@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/eae5b849-f1db-43f5-af88-424a6b04890b%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>>
>> Justin Beckwith | Google Cloud Platform | @justinbeckwith 
>>  | http://jbeckwith.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 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/27920f65-85d7-4833-9c9e-72e880a677a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Stanislas,

Great to hear. I think you'll be glad you did, from what I see the 
flexibility and power of kubernetes is something really amazing if you can 
leverage it. Feel free to post to the kubernetes-users 
<https://groups.google.com/forum/#!forum/kubernetes-users> group forum if 
you have any open-ended discussions or questions about this. 
Troubleshooting can be done on Stack Overflow <http://stackoverflow.com> 
and issues can be reported at the issuetracker.google.com.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, April 6, 2017 at 4:27:30 AM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> Thank you so much for your time and detailed explanations. I've been 
> investigating GKE and it seems like it strikes the right balance between 
> speed and convenience, so I'll probably move progressively towards it.
> Best,
>
> On Thu, Apr 6, 2017 at 1:28 AM 'Nick (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Stanislas,
>>
>> So, I can confirm that my prior investigation and intuitions were on the 
>> right track. I can confirm that a majority of deployment lag comes from 
>> programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
>> in this case. Updates have to go out across the entire infrastructure while 
>> still respecting certain locks used to keep configurations consistent. 
>> These Load Balancers are not visible to users in the Console and not 
>> user-configurable as they're infrastructural and meant to be exactly as 
>> they are, else users may try to modify or accidentally delete them, which 
>> would cause a lot of issues.
>>
>> We're devoting a lot of energy to decreasing GCLB configuration push 
>> times, so rest assured that our efforts in that direction should pay off 
>> going forward.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>>>
>>> Great, thank you so much for your help, I'll be very interested in the 
>>> details you'll get from your investigation.
>>>
>>> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via 
>>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>>
>>>> Hey Stanislas,
>>>>
>>>> The exact explanation speculated on in my last post shouldn't be taken 
>>>> as any description of what's necessarily going on, however it was an 
>>>> estimate of what might be happening based on the logs observed. I'm 
>>>> corresponding with experts in this area to get a more clear answer at the 
>>>> moment. 
>>>>
>>>> You could look into deploying on Container Engine 
>>>> <https://cloud.google.com/container-engine/>, which would mean that 
>>>> the front-end management done by the App Engine Flexible Environment 
>>>> infrastructure wouldn't be happening, rather it would be the 
>>>> responsibility 
>>>> of the resources you deploy on Container Engine (a managed service based 
>>>> pretty transparently on Kubernetes <https://kubernetes.io/>). Surely 
>>>> deploying new container images to your pool of instances in a cluster (or 
>>>> multiple clusters) would be quite fast, since the master sitting in front 
>>>> of your clusters and the nodes in the cluster are not as massively 
>>>> distributed as the App Engine Flexible Environment serving infrastructure, 
>>>> hence updating their routing rules would be relatively fast. This is 
>>>> something to look into and experiment with if you don't want to wait on 
>>>> the 
>>>> more detailed word from experts, but don't rush to that if you're not all 
>>>> that curious.
>>>>
>>>> I'll get back to this thread with more details when they're forthcoming 
>>>> in our investigation.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Support 
>>>>
>>>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:
>>>>>
>>>>> Hi Nick,
>>>>> Thanks a lot for the lengthy explanation. 
>>>>> In this light, is there anything I can do to speed things up? Like for 
>>>>> instance take care of the load-balancer myself? Indeed I don't see a 
>>>>> reason 
>>>>> why it should need to be changed. Could I do this with GAE or would I 
>>>

[google-appengine] Re: Speech API - word timings

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Lance,

We're aware of this request although we can't provide any timelines on our 
work, across any products. If you'd like, you can "star" this issue by 
hitting "Me Too" in the Public Issue Tracker 
<https://b.corp.google.com/issues/37002743>.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, April 4, 2017 at 4:59:56 AM UTC-4, Lance Dolan wrote:
>
> What is the latest news on this feature?
>
> We're evaluating Google Speech API as a means for a rather large solution. 
> Google is more accurate than its competitors, but the competitors prove 
> word timings. For example, see IBM Watson here, and click the "word 
> timings" tab (https://speech-to-text-demo.mybluemix.net). It functions 
> almost exactly as Gene has requested here.
>
> For us, knowing word timings is a requirement... To proceed with Google 
> Speech might require some really hacky weird stuff on our part to determine 
> timings. We've tested chopping the audio up in to 3 second blocks to create 
> our own rough estimate of timings, but this dramatically harms the accuracy 
> as the Google service loses its context for each audio block.
>
> On Friday, August 19, 2016 at 11:16:28 AM UTC-7, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Gene,
>>
>> Final update for now, the issue is filed and will be taken a look at. 
>>
>> Have a nice day!
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Monday, August 8, 2016 at 11:32:28 AM UTC-4, Gene Matocha wrote:
>>>
>>> Hi,
>>>
>>> Just stareted evaluating the Google Speech API. The accuracy is 
>>> impressive, but it doesn't provide word timings (when in the recording the 
>>> word occurred)  by default, and I don't see it as a configurable option. 
>>> Does anyone know if this can be enabled, or may be on the roadmap for a 
>>> future release?
>>>
>>> Thanks,
>>> Gene
>>>
>>

-- 
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/2f386947-a589-46a2-9ed3-d5759c86b118%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Stanislas,

So, I can confirm that my prior investigation and intuitions were on the 
right track. I can confirm that a majority of deployment lag comes from 
programming the Google Cloud Load Balancers (GCLB). This is what we've seen 
in this case. Updates have to go out across the entire infrastructure while 
still respecting certain locks used to keep configurations consistent. 
These Load Balancers are not visible to users in the Console and not 
user-configurable as they're infrastructural and meant to be exactly as 
they are, else users may try to modify or accidentally delete them, which 
would cause a lot of issues.

We're devoting a lot of energy to decreasing GCLB configuration push times, 
so rest assured that our efforts in that direction should pay off going 
forward.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 21, 2017 at 6:41:52 PM UTC-4, Stanislas Marion wrote:
>
> Great, thank you so much for your help, I'll be very interested in the 
> details you'll get from your investigation.
>
> On Tue, Mar 21, 2017 at 9:22 PM 'Nick (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Stanislas,
>>
>> The exact explanation speculated on in my last post shouldn't be taken as 
>> any description of what's necessarily going on, however it was an estimate 
>> of what might be happening based on the logs observed. I'm corresponding 
>> with experts in this area to get a more clear answer at the moment. 
>>
>> You could look into deploying on Container Engine 
>> <https://cloud.google.com/container-engine/>, which would mean that the 
>> front-end management done by the App Engine Flexible Environment 
>> infrastructure wouldn't be happening, rather it would be the responsibility 
>> of the resources you deploy on Container Engine (a managed service based 
>> pretty transparently on Kubernetes <https://kubernetes.io/>). Surely 
>> deploying new container images to your pool of instances in a cluster (or 
>> multiple clusters) would be quite fast, since the master sitting in front 
>> of your clusters and the nodes in the cluster are not as massively 
>> distributed as the App Engine Flexible Environment serving infrastructure, 
>> hence updating their routing rules would be relatively fast. This is 
>> something to look into and experiment with if you don't want to wait on the 
>> more detailed word from experts, but don't rush to that if you're not all 
>> that curious.
>>
>> I'll get back to this thread with more details when they're forthcoming 
>> in our investigation.
>>
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support 
>>
>> On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:
>>>
>>> Hi Nick,
>>> Thanks a lot for the lengthy explanation. 
>>> In this light, is there anything I can do to speed things up? Like for 
>>> instance take care of the load-balancer myself? Indeed I don't see a reason 
>>> why it should need to be changed. Could I do this with GAE or would I have 
>>> to move to G Container/Compute E?
>>> Cheers,
>>>
>>> On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via 
>>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>>
>>>> Hey Stanislas,
>>>>
>>>> My initial hunch was that the issue was the deployment of other 
>>>> resources necessary to support the containers running. My analysis of 
>>>> deployment-related logs appears to confirm this:
>>>>
>>>> I created a simple NodeJS app using your dockerfile and default.yaml. I 
>>>> then pushed the docker image to gcr.io and ran "gcloud app deploy 
>>>> --image-url ..."
>>>>
>>>> After about 1 minute of waiting, all resources associated with the 
>>>> deployment had apparently completed, but the command had not returned yet:
>>>>
>>>> ```
>>>> $ gcloud deployment-manager resources list --deployment 
>>>> aef-default-20170321t185300
>>>>
>>>> NAME   TYPE 
>>>> STATE  ERRORS  INTENT
>>>> aef-default-20170321t185300-00 
>>>> compute.beta.regionInstanceGroupManager  COMPLETED  []
>>>> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck 
>>>>  COMPLETED  []
>>>> aef-default-20170321t185300-00it   compute.v1.instanceTemplate 
>>>>  COMPLETED  []
>>>> a

[google-appengine] Re: Sudden import errors in unmodified Python 2.7 applications since the past few hours.

['Nick (Cloud Platform Support)' via Google App Engine]

@Richard specifically,

Do you think you could post the details of this patch you apply after each 
upgrade? This sounds like a feature request in the making.

On Thursday, March 30, 2017 at 3:56:03 AM UTC-4, Richard Cheesmar wrote:
>
> Hi, Nick, I've been got the same evening/morning 29th 30th March. Some 
> continuous errors all of the the ImportError: No module named pwd kind.
>
> I get this with the dev environment everytime I upgrade to a new version 
> of the cloud software, but that is solved by white listing pwd in one of 
> the local Google Cloud setting files, can't remember which at the moment.
>
> Never had this on the live environment though.
>
> On Tuesday, March 28, 2017 at 12:45:22 PM UTC+3, rrk wrote:
>>
>> Hi,
>>
>> Anyone else facing sudden ImportError issues with previously working 
>> applications in Python 2.7 runtime of Google App Engine?
>>
>> One such error is given below, which happens when *requests *package is 
>> trying to import *netrc*. This code was working fine until today. 
>>
>> Traceback (most recent call last):
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 240, in Handle
>>
>> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 299, in _LoadHandler
>>
>> handler, path, err = LoadObject(self._handler)
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 85, in LoadObject
>>
>> obj = __import__(path[0])
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/x.py",
>>  
>> line 36, in 
>>
>> from yy import *
>>
>>   File "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/
>> yy.py", line 32, in 
>>
>> import requests
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/__init__.py",
>>  
>> line 52, in 
>>
>> from . import utils
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/utils.py",
>>  
>> line 19, in 
>>
>> from netrc import netrc, NetrcParseError
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>>  
>> line 7, in 
>>
>> import pwd
>>
>> ImportError: No module named pwd
>>
>>
>> I have the same application deployed for other customers within their 
>> accounts and also in my account, but this error seems to have occurred only 
>> for one deployment.
>>
>> Why is this happening? Does this have something to do with the 
>> python27_experiment version, which I believe has been in use since over 
>> a month (based on error traces on the internet with this version), but this 
>> ImportError seems to have got triggered only today? May be my client's 
>> application has been included within the experimental version?
>>
>> Thanks and regards,
>> Raj
>>
>

-- 
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/8c0ffdbc-84e6-4b86-ab29-c816f44b884d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sudden import errors in unmodified Python 2.7 applications since the past few hours.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Folks,
 
The root cause of this issue has been identified and we're in the process 
of rolling out a fix. Please check in to this thread and let us know if 
this issue persists, and email me your project ID at pay...@google.com if 
so.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 30, 2017 at 3:56:03 AM UTC-4, Richard Cheesmar wrote:
>
> Hi, Nick, I've been got the same evening/morning 29th 30th March. Some 
> continuous errors all of the the ImportError: No module named pwd kind.
>
> I get this with the dev environment everytime I upgrade to a new version 
> of the cloud software, but that is solved by white listing pwd in one of 
> the local Google Cloud setting files, can't remember which at the moment.
>
> Never had this on the live environment though.
>
> On Tuesday, March 28, 2017 at 12:45:22 PM UTC+3, rrk wrote:
>>
>> Hi,
>>
>> Anyone else facing sudden ImportError issues with previously working 
>> applications in Python 2.7 runtime of Google App Engine?
>>
>> One such error is given below, which happens when *requests *package is 
>> trying to import *netrc*. This code was working fine until today. 
>>
>> Traceback (most recent call last):
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 240, in Handle
>>
>> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 299, in _LoadHandler
>>
>> handler, path, err = LoadObject(self._handler)
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 85, in LoadObject
>>
>> obj = __import__(path[0])
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/x.py",
>>  
>> line 36, in 
>>
>> from yy import *
>>
>>   File "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/
>> yy.py", line 32, in 
>>
>> import requests
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/__init__.py",
>>  
>> line 52, in 
>>
>> from . import utils
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/utils.py",
>>  
>> line 19, in 
>>
>> from netrc import netrc, NetrcParseError
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>>  
>> line 7, in 
>>
>> import pwd
>>
>> ImportError: No module named pwd
>>
>>
>> I have the same application deployed for other customers within their 
>> accounts and also in my account, but this error seems to have occurred only 
>> for one deployment.
>>
>> Why is this happening? Does this have something to do with the 
>> python27_experiment version, which I believe has been in use since over 
>> a month (based on error traces on the internet with this version), but this 
>> ImportError seems to have got triggered only today? May be my client's 
>> application has been included within the experimental version?
>>
>> Thanks and regards,
>> Raj
>>
>

-- 
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/85b701df-2316-4532-bab7-1ad9bf9846fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error occurs after 30-40 consecutive urlfetch

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Chris,

>From reading the thread history, it seems that there are potentially two 
issues brought up by kyeongwook Ma and Dustin Oprea. Although both see an 
expired context, one is about UrlFetch calls and the other is about 
Datastore API calls. The mechanism underlying potentially both of them, if 
they *are* the same issue, was discussed as being the duration of the 
request handler. 

In your case, we haven't got from your post any details other than that you 
see this error (exactly as posted by OP? or a similar error?) quite often 
(how often?) and that your request handler runs under a second. This last 
fact certainly rules out a request deadline root cause, but leaves a lot 
undefined. 

Given that this thread seems to have exhausted itself and in the first 
place was not suited to this forum (which is meant for general discussion, 
not technical support or issue tracking, for which we have Stack Overflow 
 and the Public Issue Tracker 
, respectively), I'd suggest posting to the 
Public Issue Tracker with as many technical details about what's occurring 
as possible. This is the surest way for us to be able to begin looking into 
the root cause. 

Finally, rest assured that we monitor our Stack Overflow tags and the 
Public Issue Tracker thoroughly - this isn't a redirect into the void but 
rather simply a question of directing you to the forum among those we 
monitor where we ourselves can best provide assistance.

Cheers

Nick
Cloud Platform Community Support



On Friday, March 31, 2017 at 1:44:10 PM UTC-4, Chris Olsen wrote:
>
> I get this error quite often as well. I am using standard environment, and 
> as was mentioned, the request itself is not a long one, but under a second.
>
> On Tuesday, August 9, 2016 at 8:29:30 AM UTC-6, kyeongwook Ma wrote:
>>
>> Hi GAE support,
>>
>> I am a developer using the GAE with Golang and gin.
>>
>> I included urlfetch in the service to use a third party service (for 
>> example, AWS SNS push service).
>>
>> The urlfetch is successful for the first few times, but when we send 
>> 30-40 consecutive urlfetch, it keeps on giving an error.
>>
>> The specific error message is:
>>
>> *WARNING  2016-08-09 13:29:56,592 urlfetch_stub.py:540] Stripped 
>> prohibited headers from URLFetch request: ['Content-Length']*
>> *ERROR: context expired before API call urlfetch/Fetch completed*
>>
>> *RequestError: send request failed*
>> *caused by: Post https://sns.us-west-1.amazonaws.com/ 
>> : Call error 3: invalid security 
>> ticket (context expired)*
>>
>> We also tested urlfetch with other third party services, and we still get 
>> the same error messages as above.
>>  
>> Is there anybody that can help us with this situation?
>>
>> Thank you very much for your help.
>>
>> Best,
>> Rio
>>
>

-- 
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/320cff12-0635-4fe9-ad55-ecfa886eaca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Strange behaviour related to java Endpoints V2

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Þórir,

This is perfect as an issue report for the Public Issue Tracker 
, where we work with users to notify 
product teams and engineering of issues on the platform. Feel free to post 
this there and we'll be able to take a look. I can't say I've seen anything 
like this before. Be sure to include all the details given in this report. 
We may ask for you to reply to a private email we'll send if we require 
copies of the logs or your code.

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 31, 2017 at 8:07:18 AM UTC-4, Þórir Gunnarsson wrote:
>
> Hi
>
> Just wanted to check with the group if anyone is experiencing unusual 
> behaviour related to endpoints v2 on AppEngine. We are using the AppEngine 
> standard environment.
>
> This morning we start getting reports from users where our Android client 
> is crashing a lot. Upon investigation we discover that yesterday 
> (30.03.2017) at 16:36 UTC we start getting unusual entries in the log that 
> look like this:
> /_ah/api/appendpoint/v8/users//dashboarddata
> and a HTTP 302 response according to the logs (this then results in a 
> crash in the Android client, which is a different story)
> On a regular day and most of the time this call from the client looks like 
> this.
> /_ah/spi/is.app.services.dashboard.DashboardEndpointV9.getDashboardData
>
> The strange thing here is the format of the log entry which is consistent 
> with the format of log entries after upgrading to endpoints v2. 
>
> We see the same exact Android client making this call and once in a while 
> it seems to get the new type of response (the endpoints v2 type log entry 
> and a 302).
>
> We did not deploy anything at this time yesterday and we were certainly 
> not using endpoints v2 at that time.
>
> After some testing we have now improved the situation by upgrading our 
> backend to using endpoints v2 (version 2.0.5). 
> I say improved because now most log entries look like they are coming from 
> endpoints v2 but once in a while we get the old style log entries and now 
> the old style log entries return 302 (according to server logs)
> The Android client no longer crashes but doesn't receive a response when 
> this happens.
>
> To further investigate what was happening we plugged in a http proxy to 
> see exactly what was going on.
> On a successful call there is a GET call to the server with a proper HTTP 
> 200 OK response
> On a failure there is a GET call to the server with a HTTP 404 NOT FOUND 
> response and an "unsupportedProtocol" error.
> We don't see any difference between the two calls. The server logs tell us 
> that both are served by the same instance on the backend.
>
>  
> So is anyone experiencing something similar?
> Should we pin this on some Google update or possibly some misconfiguration 
> on our end?
>
>
>

-- 
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/13dd22dd-d06e-49b2-bfe3-2cd79237ee95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Dewey,

That's an interesting pattern I can't say I've seen before. Now that you 
provide more details I see what you meant in your original post. I've 
attempted to reproduce this issue but haven't been able to observe it 
occurring. If you want to file a Feature Request for a better error message 
in the Public Issue Tracker , be sure to 
include a reproducing example app (you can produce this by stripping 
everything from your app that's proprietary / not necessary for reproducing 
the issue). We monitor the Public Issue Tracker regularly and would be 
happy to take your report.
 
Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 30, 2017 at 12:29:13 AM UTC-4, Dewey Gaedcke wrote:
>
> Hi Nick...thanks for your reply.
>
> I did also post this to SO but have received no responsesseems no one 
> else has seen this
> And since my code did not change, but I had recently upgraded the SDK, I 
> was unclear what was causing the problem.  But here is the summary:
>
> the backend for our mobile app (under app.yaml) calls these two lines:
> from google.appengine.api import taskqueue
> taskqueue.add(target='task', queue_name=GAEQ_FOR_PUSH_NOTIFY, url=url,
> params=params )
>
> That taskqueue.add() caused the error & resulting stack-trace shown above.
>
> I had been starting my local dev-server via CLI like this:
>
> dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
> --logs_path=/tmp/gaelogs --log_level=debug
>
>
> I didn't realize that I had grabbed an old example from our dev-onboarding 
> document...and I should have been starting the local server like this:
>
>
> dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
> service_task.yaml --logs_path=/tmp/gaelogs --log_level=debug
>
>
> once I also started the task microservice, the crash disappearedor at 
> least I've not seen it again
>
>
> service_task.yaml is the one that includes:
>
> - url: /_ah/queue/deferred
>   script: google.appengine.ext.deferred.handler
>   login: admin
>
> in the handlers section
>
>
> all I can guess is that this caused the local environment to start up the 
> task queuebut I really am only guessing...
>

-- 
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/ef68ecd0-88d9-488e-ad7f-11c36feed96b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Error when using google.cloud.logging with logging.v1.RequestLog?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Julian,

It seems more likely to be an issue with the shell in Windows rather than 
the SDK, but of course if you can determine that it's not the shell, then 
you'd want to post this as an issue to the Public Issue Tracker 
<http://issuetracker.google.com> with all information necessary for us to 
attempt to observe this on our own systems. Stack Overflow is a good choice 
when you aren't sure if it's a platform issue or just your own code / 
configuration.

As for the quoting issue, I'm no windows expert but I thought I did 
remember something about quote escaping being weird in CMD. Lo and behold, 
there's a Stack Overflow Q <http://stackoverflow.com/a/15262019/4270992> 
about this, maybe your solution is in there? It seems that the way to 
escape a quote is to just put two quotes, but if it was that simple, the 
answer wouldn't be so long. Happy reading!

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 4:07:34 PM UTC-4, Julian Bunn wrote:
>
> Hi Nick,
>
> Thanks - I had just started doing exactly what you suggest! :-)
>
> I crave your indulgence on one other issue ... when I run a gcloud beta 
> logging command with a LOG_FILTER clause on a Unix system, it works fine. 
> For example:
>
>  gcloud beta logging read 'timestamp<="2017-03-23T00:00:00Z" AND 
> timestamp>="2017-03-22T00:00:00Z"' --limit=2
>
> However, on Windows, the exact same command doesn't work - I suspect the 
> single and double quotes are part of the problem:
>
>  gcloud beta logging read 'timestamp<="2017-03-23T00:00:00Z" AND 
> timestamp>="2017-03-22T00:00:00Z"' --limit=2
> The filename, directory name, or volume label syntax is incorrect.
>
> (A simple "gcloud beta logging read" works just fine on Windows.)
>
> I've tried various ways of escaping the quotes, but nothing appears to 
> work.
>
> Should I post this on StackOverflow?
>
>
>
>
> On Wed, Mar 29, 2017 at 12:37 PM, 'Nick (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Julian,
>>
>> You have two options here: either to wait for the google.cloud library to 
>> get support for V1 logs, or adopt a slightly different approach to writing 
>> the python script. You could use the python subprocess 
>> <https://docs.python.org/2/library/subprocess.html> module to call the 
>> gcloud command (keeping in mind that this is part of the beta command 
>> group, which can change on updates without warning (the only warning being 
>> the release notes)), sending the output into a string, and then parsing the 
>> entries that way. This, while it would mean you'd have your logs in a 
>> python environment (with all the leverage that brings) however would not 
>> use the google.cloud library.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, March 28, 2017 at 5:51:54 PM UTC-4, Julian Bunn wrote:
>>>
>>> Thanks, Nick!
>>>
>>> I confirm that the command "gcloud beta logging read" retrieves our 
>>> logs! So this looks very promising ...
>>>
>>> Is there a way to call this interface similarly to:
>>>
>>> from google.cloud import logging
>>> from google.cloud.logging import DESCENDING
>>> def main():
>>> client = logging.Client() 
>>> for entry in client.list_entries(order_by=DESCENDING):
>>> print entry
>>> if __name__ == '__main__':
>>> main()
>>>
>>>
>>>
>>> On Tue, Mar 28, 2017 at 12:39 PM, 'Nick (Cloud Platform Support)' via 
>>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>>
>>>> Hey Julian,
>>>>
>>>> I've observed the identical error when using the filter 
>>>> 'resource.type="gae_app" 
>>>> AND resource.labels.module_id="default"', where I'd deployed a 
>>>> standard environment app on "default". 
>>>>
>>>> It appears this is caused by the fact that the standard environment 
>>>> doesn't log to Stackdriver v2 logging, as you observed. The docs show all 
>>>> v2 endpoints are what the library interfaces with. Nonetheless, it should 
>>>> be able to read V1 type logs as well, or at least we can consider this a 
>>>> feature request. 
>>>>
>>>> In the meantime, the following command pattern can be used, presenting 
>>>> no problem with V1 logs:
>>>>
>>>> gcloud beta logging read ${LOG_FILTER}
>>>&g

Re: [google-appengine] Re: App Engine Admin API Error - The "appengine.applications.create" permission is required.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Ulapph,

Great, I've posted an answer to your question there (although you'll notice 
I'd also posted it here).

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 3:54:06 PM UTC-4, Ulapph Corporation wrote:
>
> Thanks Nick!
> Here is the link to the StackOverflow question...
>
> http://stackoverflow.com/questions/43080487/app-engine-admin-api-error-the-appengine-applications-create-permission-is-r
>
>
> On Thu, Mar 30, 2017 at 3:08 AM, 'Nick (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Ulapph,
>>
>> This forum is not meant for technical support requests, and should be 
>> used instead for general discussions of the platform and services. Your 
>> question seems perfect for posting to stackoverflow.com, where we also 
>> monitor various tags officially sponsored by Google Cloud Platform. 
>>
>> Feel free to post a link to your question in this thread once you've 
>> posted to Stack Overflow, and I'll be happy to assist in the proper forum. 
>>
>> I can give this small piece of advice before then, however: it seems 
>> you've given no details about how you set up the account you're using to 
>> authorize the request. You'll need to make sure the 
>> appengine.applications.create permission is given to the account you're 
>> using, as mentioned in the error text. You can use the Google Identity 
>> and Access Management (IAM) API 
>> <https://cloud.google.com/iam/reference/rest/> for this.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, March 28, 2017 at 5:34:52 PM UTC-4, Ulapph Corporation wrote:
>>>
>>> Hi,
>>>
>>> We would like to automatically create a project ID and install our 
>>> ULAPPH Cloud Desktop application using the App Engine Admin API (REST) and 
>>> Golang.
>>>
>>> https://cloud.google.com/appengine/docs/admin-api/?hl=en_US&_ga=1.265860687.1935695756.1490699302
>>>
>>> https://ulapph-public-1.appspot.com/articles?TYPE=ARTICLE_ID=3=TDSARTL-3
>>>
>>> We were able to get a token but when we tried to create a project ID, we 
>>> get the error below.
>>>
>>> [Response OK] Successful connection to Appengine Admin API.
>>> [Token] { "access_token" : "TOKEN_HERE", "expires_in" : 3599, 
>>> "token_type" : "Bearer" }
>>> [Response Code] 403
>>> [Response Body] { "error": { "code": 403, "message": "Operation not 
>>> allowed", "status": "PERMISSION_DENIED", "details": [ { "@type": "
>>> type.googleapis.com/google.rpc.ResourceInfo", "resourceType": 
>>> "gae.api", "description": "The \"appengine.applications.create\" permission 
>>> is required." } ] } }
>>>
>>> We are just using the REST API calls. Request for token was successful 
>>> as you can see above and the scope is ok as well. Now, when we posted the 
>>> request to create application, we are having the error that says 
>>> "appengine.application.create" permission required. 
>>>
>>> How do we specify the permission? What are the possible reasons why we 
>>> are getting that error? Do we missed to send a field in JSON or in query?
>>>
>>> As per below link, we just need to pass the json containing the id and 
>>> location. We also just need to pass the token. The same logic I have used 
>>> successfully in accessing Youtube, Drive APIs so not sure what needs to be 
>>> done since I have followed the docs available.
>>>
>>> Best Regards,
>>> ULAPPH
>>>
>> -- 
>> 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/DvXFJBeVC5w/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 https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/06298cee-b3db-4557-80b7-622c5e5118e2%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/06298cee-b3db-4557-80b7-622c5e5118e2%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Best Regards,
>
> ULAPPH Corporation
> http://www.ulapph.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 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/86fc3c45-0efd-487a-9caf-72665b6d3958%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Error when using google.cloud.logging with logging.v1.RequestLog?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Julian,

You have two options here: either to wait for the google.cloud library to 
get support for V1 logs, or adopt a slightly different approach to writing 
the python script. You could use the python subprocess 
<https://docs.python.org/2/library/subprocess.html> module to call the 
gcloud command (keeping in mind that this is part of the beta command 
group, which can change on updates without warning (the only warning being 
the release notes)), sending the output into a string, and then parsing the 
entries that way. This, while it would mean you'd have your logs in a 
python environment (with all the leverage that brings) however would not 
use the google.cloud library.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 28, 2017 at 5:51:54 PM UTC-4, Julian Bunn wrote:
>
> Thanks, Nick!
>
> I confirm that the command "gcloud beta logging read" retrieves our logs! 
> So this looks very promising ...
>
> Is there a way to call this interface similarly to:
>
> from google.cloud import logging
> from google.cloud.logging import DESCENDING
> def main():
> client = logging.Client() 
> for entry in client.list_entries(order_by=DESCENDING):
> print entry
> if __name__ == '__main__':
>     main()
>
>
>
> On Tue, Mar 28, 2017 at 12:39 PM, 'Nick (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Julian,
>>
>> I've observed the identical error when using the filter 
>> 'resource.type="gae_app" 
>> AND resource.labels.module_id="default"', where I'd deployed a standard 
>> environment app on "default". 
>>
>> It appears this is caused by the fact that the standard environment 
>> doesn't log to Stackdriver v2 logging, as you observed. The docs show all 
>> v2 endpoints are what the library interfaces with. Nonetheless, it should 
>> be able to read V1 type logs as well, or at least we can consider this a 
>> feature request. 
>>
>> In the meantime, the following command pattern can be used, presenting no 
>> problem with V1 logs:
>>
>> gcloud beta logging read ${LOG_FILTER}
>>
>>
>> I've created a Public Issue Tracker issue 
>> <https://b.corp.google.com/issues/36687054> which you can follow while 
>> we work on this.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Monday, March 27, 2017 at 3:14:13 PM UTC-4, Julian Bunn wrote:
>>>
>>> Hi Nick,
>>>
>>> Thanks ... I do try StackOverflow from time to time for these sorts of 
>>> technical issues, but have very limited success. Perhaps I'm using bad 
>>> tags. See for example a logging related question I posted there on Friday 
>>> about JSON credentials for logging 
>>> https://stackoverflow.com/questions/43004904/accessing-gae-log-files-using-google-cloud-logging-python
>>>
>>> Regarding the v1.RequestLog error that's the topic of this thread: we do 
>>> not use StackDriver logging in our GAE deployment, so I wonder whether 
>>> cloud.logging only supports StackDriver logs?
>>>
>>> Otherwise, I am at a loss as to why google.cloud.logging can't 
>>> understand the log format it fetches from our GAE deployment?
>>>
>>> We've now been without access to our log data for almost a week, so I'm 
>>> getting quite desperate to find a solution either with request_logs or 
>>> cloud.logging :-)
>>>
>>> Thanks for your help.
>>>
>>> Julian
>>>
>>>
>>>
>>>
>>> On Mon, Mar 27, 2017 at 11:58 AM, 'Nick (Cloud Platform Support)' via 
>>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>>
>>>> Hey Julian,
>>>>
>>>> I've been able just now to run the same code fine. What might you mean 
>>>> by "the type of logging we use on GAE"? Are you doing anything 
>>>> particularly 
>>>> odd there?
>>>>
>>>> It's worth mentioning here that this forum isn't meant for technical 
>>>> support but rather for general discussion of the platform, services, 
>>>> design 
>>>> patterns, etc. This question should have been posted to 
>>>> stackoverflow.com on a relevant Cloud Platform / App Engine tag. We 
>>>> monitor Stack Overflow regularly, so we'll be able to answer there, 
>>>> although we can perhaps help debug this a little here before you move to 
>>>> post there.
>>>>
>>>> Cheers,
>>>&

[google-appengine] Re: App Engine Admin API Error - The "appengine.applications.create" permission is required.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Ulapph,

This forum is not meant for technical support requests, and should be used 
instead for general discussions of the platform and services. Your question 
seems perfect for posting to stackoverflow.com, where we also monitor 
various tags officially sponsored by Google Cloud Platform. 

Feel free to post a link to your question in this thread once you've posted 
to Stack Overflow, and I'll be happy to assist in the proper forum. 

I can give this small piece of advice before then, however: it seems you've 
given no details about how you set up the account you're using to authorize 
the request. You'll need to make sure the appengine.applications.create 
permission is given to the account you're using, as mentioned in the error 
text. You can use the Google Identity and Access Management (IAM) API 
 for this.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 28, 2017 at 5:34:52 PM UTC-4, Ulapph Corporation wrote:
>
> Hi,
>
> We would like to automatically create a project ID and install our ULAPPH 
> Cloud Desktop application using the App Engine Admin API (REST) and Golang.
>
> https://cloud.google.com/appengine/docs/admin-api/?hl=en_US&_ga=1.265860687.1935695756.1490699302
>
> https://ulapph-public-1.appspot.com/articles?TYPE=ARTICLE_ID=3=TDSARTL-3
>
> We were able to get a token but when we tried to create a project ID, we 
> get the error below.
>
> [Response OK] Successful connection to Appengine Admin API.
> [Token] { "access_token" : "TOKEN_HERE", "expires_in" : 3599, "token_type" 
> : "Bearer" }
> [Response Code] 403
> [Response Body] { "error": { "code": 403, "message": "Operation not 
> allowed", "status": "PERMISSION_DENIED", "details": [ { "@type": "
> type.googleapis.com/google.rpc.ResourceInfo", "resourceType": "gae.api", 
> "description": "The \"appengine.applications.create\" permission is 
> required." } ] } }
>
> We are just using the REST API calls. Request for token was successful as 
> you can see above and the scope is ok as well. Now, when we posted the 
> request to create application, we are having the error that says 
> "appengine.application.create" permission required. 
>
> How do we specify the permission? What are the possible reasons why we are 
> getting that error? Do we missed to send a field in JSON or in query?
>
> As per below link, we just need to pass the json containing the id and 
> location. We also just need to pass the token. The same logic I have used 
> successfully in accessing Youtube, Drive APIs so not sure what needs to be 
> done since I have followed the docs available.
>
> Best Regards,
> ULAPPH
>

-- 
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/06298cee-b3db-4557-80b7-622c5e5118e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Dewey,

A thread like this, asking for technical support without determining 
whether it's the responsibility of your code or an issue with the platform 
/ SDK itself, should be made to Stack Overflow. An issue which you've 
determined to be in our code / within our responsibility to fix, should be 
posted to the Public Issue Tracker. This forum is not meant for technical 
support or issue reporting, but is meant for general and high level 
discussion of the platform and services, less specific and goal directed 
threads to which many users can contribute. 

I'd like to create a Feature Request in the Public Issue Tracker 
 from your post here to show an example of 
how to file a feature request for more clear errors once we've determined 
that an error needs a more clear message. The issue is, I'm not quite sure 
what was going wrong or what you did to fix it. Could you clarify what you 
saw, what you expected to see, what you saw instead, and what you did to 
change the issue?

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 1:07:42 PM UTC-4, Dewey Gaedcke wrote:
>
> OKI found the problem. The dev server was starting up without the 
> taskqueue server running and so I guess the whole taskqueue package was not 
> added to the google.api package
>
> Seems like a better error would be useful in that case
>

-- 
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/7d636a50-557f-4485-a02c-41d505e3fb52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: where do I find the build logs?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Marco,

There are no bad questions! You can check the Cloud Console 
 > "Logs" section and select "Container 
Builder" as the logs source. You can further select more granularly by 
build id, which will be given when you run the deployment, in a line like 
the following: 

starting build "a7fccbd5-1d13-4b95-9c2a-3c13c77fc3b2"


Actually, the deploy command should also present a line like the following 
which will take you directly to the relevant logs:

To see logs in the Cloud Console: 
https://console.cloud.google.com/logs/viewer?project=wheel-of-time-8=build_id=a7fccbd5-1d13-4b95-9c2a-3c13c77fc3b2=build%2Fbuild_id%2Fa7fccbd5-1d13-4b95-9c2a-3c13c77fc3b2


You could also run the following gcloud command:


gcloud beta logging read "resource.type=\"build\" AND 
resource.labels.build_id=\"${YOUR_DEPLOYMENT'S_BUILD_ID}\""


I've highlighted in yellow the filter portion of this command. You can read 
about the command by running "gcloud beta logging read --help" or in the 
relevant online documentation 
. For more 
information on forming filters (which can also be used in the Console logs 
viewer), you can read the documentation under "Advanced Logs Filters 
".

Cheers,

Nick
Cloud Platform Community Support



On Wednesday, March 29, 2017 at 3:54:59 AM UTC-4, Marco Galassi wrote:
>
> I am not able to deploy for some error. At the end of the deployment 
> process i get:
>
> ERROR: (gcloud.app.deploy) Error Response: [2] Build failed; check build 
> logs for details
>
> This is very stupid, but where do I find the build logs?
>

-- 
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/13e96556-7612-47e6-85f9-455aec4b6b38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sudden import errors in unmodified Python 2.7 applications since the past few hours.

['Nick (Cloud Platform Support)' via Google App Engine]

We're currently looking into the possible causes for this behaviour and 
hope to be able to update this thread shortly. Thanks for your patience!

On Wednesday, March 29, 2017 at 10:47:26 AM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Hey Dima,
>
> I've sent you an email from esupp...@google.com as well, as Raj has not 
> responded to the initial email. Generally, something like this should be 
> posted to the Public Issue Tracker <http://issuetracker.google.com> if 
> you've determined that it's unlikely to be resolvable or a consequence of 
> your own code. 
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Wednesday, March 29, 2017 at 8:49:12 AM UTC-4, Dima Gimburg wrote:
>>
>> Hi Raj, did you manage to fix this issue?
>>
>> On Tuesday, March 28, 2017 at 9:45:22 AM UTC, rrk wrote:
>>>
>>> Hi,
>>>
>>> Anyone else facing sudden ImportError issues with previously working 
>>> applications in Python 2.7 runtime of Google App Engine?
>>>
>>> One such error is given below, which happens when *requests *package is 
>>> trying to import *netrc*. This code was working fine until today. 
>>>
>>> Traceback (most recent call last):
>>>
>>>   File 
>>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>>  
>>> line 240, in Handle
>>>
>>> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>>>
>>>   File 
>>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>>  
>>> line 299, in _LoadHandler
>>>
>>> handler, path, err = LoadObject(self._handler)
>>>
>>>   File 
>>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>>  
>>> line 85, in LoadObject
>>>
>>> obj = __import__(path[0])
>>>
>>>   File 
>>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/x.py",
>>>  
>>> line 36, in 
>>>
>>> from yy import *
>>>
>>>   File "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/
>>> yy.py", line 32, in 
>>>
>>> import requests
>>>
>>>   File 
>>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/__init__.py",
>>>  
>>> line 52, in 
>>>
>>> from . import utils
>>>
>>>   File 
>>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/utils.py",
>>>  
>>> line 19, in 
>>>
>>> from netrc import netrc, NetrcParseError
>>>
>>>   File 
>>> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>>>  
>>> line 7, in 
>>>
>>> import pwd
>>>
>>> ImportError: No module named pwd
>>>
>>>
>>> I have the same application deployed for other customers within their 
>>> accounts and also in my account, but this error seems to have occurred only 
>>> for one deployment.
>>>
>>> Why is this happening? Does this have something to do with the 
>>> python27_experiment version, which I believe has been in use since over 
>>> a month (based on error traces on the internet with this version), but this 
>>> ImportError seems to have got triggered only today? May be my client's 
>>> application has been included within the experimental version?
>>>
>>> Thanks and regards,
>>> Raj
>>>
>>

-- 
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/6b9dce98-1bdf-424f-bf91-7ebacece40ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: AppEngine no module 'pwd' using requests lib

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Dima,

We appreciate your concern to get this issue looked at. There's currently 
already a thread in these forums on the same topic, where you're active 
, and 
it's best to avoid opening multiple threads on the same topic. Rest assured 
that although this forum is not meant for technical support requests, we 
are nonetheless looking actively into the possible causes for this issue. 
Please refer to the other open thread, and be sure to open issues like this 
in the Public Issue Tracker  in future.

Regards,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 8:49:12 AM UTC-4, Dima Gimburg wrote:
>
> We are getting on one of our application this 500 error 'no module pwd' 
> when importing requests library.
> here are the logs:
>
> Traceback (most recent call last):
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 240, in Handle
> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 299, in _LoadHandler
> handler, path, err = LoadObject(self._handler)
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 96, in LoadObject
> __import__(cumulative_path)
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/handler/domain.py",
>  
> line 12, in 
> from lib.helper import TemplateHelper, RequestHandler
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/lib/helper.py",
>  
> line 13, in 
> from lib.security import Security
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/lib/security.py",
>  
> line 5, in 
> from lib.wisestamp_email_settings_client import 
> WiseStampEmailSettingsClient
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/lib/wisestamp_email_settings_client.py",
>  
> line 6, in 
> import requests
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/lib/requests/__init__.py",
>  
> line 58, in 
> from . import utils
>   File 
> "/base/data/home/apps/s~wisestamp-gapps-oath2-qa/2-42-3.400175773712341679/lib/requests/utils.py",
>  
> line 19, in 
> from netrc import netrc, NetrcParseError
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>  
> line 7, in 
> import pwd
> ImportError: No module named pwd
>
> in other project ive noticed it is not happening and there is no 
> python27_experiment dir path in the logs, are we on some kind of experiment 
> instances?
>

-- 
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/0cabff19-b724-494f-b56d-a6b309fe3664%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sudden import errors in unmodified Python 2.7 applications since the past few hours.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Dima,

I've sent you an email from esupp...@google.com as well, as Raj has not 
responded to the initial email. Generally, something like this should be 
posted to the Public Issue Tracker  if 
you've determined that it's unlikely to be resolvable or a consequence of 
your own code. 

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 8:49:12 AM UTC-4, Dima Gimburg wrote:
>
> Hi Raj, did you manage to fix this issue?
>
> On Tuesday, March 28, 2017 at 9:45:22 AM UTC, rrk wrote:
>>
>> Hi,
>>
>> Anyone else facing sudden ImportError issues with previously working 
>> applications in Python 2.7 runtime of Google App Engine?
>>
>> One such error is given below, which happens when *requests *package is 
>> trying to import *netrc*. This code was working fine until today. 
>>
>> Traceback (most recent call last):
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 240, in Handle
>>
>> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 299, in _LoadHandler
>>
>> handler, path, err = LoadObject(self._handler)
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>>  
>> line 85, in LoadObject
>>
>> obj = __import__(path[0])
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/x.py",
>>  
>> line 36, in 
>>
>> from yy import *
>>
>>   File "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/
>> yy.py", line 32, in 
>>
>> import requests
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/__init__.py",
>>  
>> line 52, in 
>>
>> from . import utils
>>
>>   File 
>> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/utils.py",
>>  
>> line 19, in 
>>
>> from netrc import netrc, NetrcParseError
>>
>>   File 
>> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>>  
>> line 7, in 
>>
>> import pwd
>>
>> ImportError: No module named pwd
>>
>>
>> I have the same application deployed for other customers within their 
>> accounts and also in my account, but this error seems to have occurred only 
>> for one deployment.
>>
>> Why is this happening? Does this have something to do with the 
>> python27_experiment version, which I believe has been in use since over 
>> a month (based on error traces on the internet with this version), but this 
>> ImportError seems to have got triggered only today? May be my client's 
>> application has been included within the experimental version?
>>
>> Thanks and regards,
>> Raj
>>
>

-- 
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/80b3c3c3-7069-4c2f-9a99-75f6fb70565d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Error when using google.cloud.logging with logging.v1.RequestLog?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Julian,

I've observed the identical error when using the filter 
'resource.type="gae_app" 
AND resource.labels.module_id="default"', where I'd deployed a standard 
environment app on "default". 

It appears this is caused by the fact that the standard environment doesn't 
log to Stackdriver v2 logging, as you observed. The docs show all v2 
endpoints are what the library interfaces with. Nonetheless, it should be 
able to read V1 type logs as well, or at least we can consider this a 
feature request. 

In the meantime, the following command pattern can be used, presenting no 
problem with V1 logs:

gcloud beta logging read ${LOG_FILTER}


I've created a Public Issue Tracker issue 
<https://b.corp.google.com/issues/36687054> which you can follow while we 
work on this.

Cheers,

Nick
Cloud Platform Community Support

On Monday, March 27, 2017 at 3:14:13 PM UTC-4, Julian Bunn wrote:
>
> Hi Nick,
>
> Thanks ... I do try StackOverflow from time to time for these sorts of 
> technical issues, but have very limited success. Perhaps I'm using bad 
> tags. See for example a logging related question I posted there on Friday 
> about JSON credentials for logging 
> https://stackoverflow.com/questions/43004904/accessing-gae-log-files-using-google-cloud-logging-python
>
> Regarding the v1.RequestLog error that's the topic of this thread: we do 
> not use StackDriver logging in our GAE deployment, so I wonder whether 
> cloud.logging only supports StackDriver logs?
>
> Otherwise, I am at a loss as to why google.cloud.logging can't understand 
> the log format it fetches from our GAE deployment?
>
> We've now been without access to our log data for almost a week, so I'm 
> getting quite desperate to find a solution either with request_logs or 
> cloud.logging :-)
>
> Thanks for your help.
>
> Julian
>
>
>
>
> On Mon, Mar 27, 2017 at 11:58 AM, 'Nick (Cloud Platform Support)' via 
> Google App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Julian,
>>
>> I've been able just now to run the same code fine. What might you mean by 
>> "the type of logging we use on GAE"? Are you doing anything particularly 
>> odd there?
>>
>> It's worth mentioning here that this forum isn't meant for technical 
>> support but rather for general discussion of the platform, services, design 
>> patterns, etc. This question should have been posted to stackoverflow.com 
>> on a relevant Cloud Platform / App Engine tag. We monitor Stack Overflow 
>> regularly, so we'll be able to answer there, although we can perhaps help 
>> debug this a little here before you move to post there.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>>
>> On Monday, March 27, 2017 at 12:25:45 PM UTC-4, Julian Bunn wrote:
>>>
>>> Right now we cannot use the request_logs feature for downloading our GAE 
>>> logs (see my other thread on that problem!), so I thought I would try the 
>>> newer google.cloud features, and get modern :-)
>>>
>>> Here is the simple test I tried:
>>>
>>> from google.cloud import logging
>>> from google.cloud.logging import DESCENDING
>>> def main():
>>> client = logging.Client() 
>>> for entry in client.list_entries(order_by=DESCENDING):
>>> print entry
>>> if __name__ == '__main__':
>>> main()
>>>
>>> When executing this (after setting up the gcloud credentials), there 
>>> seems to be a problem parsing the log entries:
>>>
>>> python GetLogsCloud.py
>>> Traceback (most recent call last):
>>>   File "GetLogsCloud.py", line 25, in 
>>> main()
>>>   File "GetLogsCloud.py", line 18, in main
>>> for entry in client.list_entries(order_by=DESCENDING):
>>>   File "c:\python27\lib\site-packages\google\cloud\iterator.py", line 
>>> 219, in _items_iter
>>> for item in page:
>>>   File "c:\python27\lib\site-packages\google\cloud\iterator.py", line 
>>> 163, in next
>>> result = self._item_to_value(self._parent, item)
>>>   File "c:\python27\lib\site-packages\google\cloud\logging\_gax.py", 
>>> line 488, in _item_to_entry
>>> resource = MessageToDict(entry_pb)
>>>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
>>> line 133, in MessageToDict
>>> return printer._MessageToJsonObject(message)
>>>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
>>> line 164, 

[google-appengine] Re: Sudden import errors in unmodified Python 2.7 applications since the past few hours.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Raj,

This should be posted to the Public Issue Tracker 
, since it appears to be an issue on the 
platform, rather than this forum which is meant for general discussion on 
the platform and services, design patterns. 

I've sent you an email from esupp...@google.com to request your project ID 
so we can take a look at this. 

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 28, 2017 at 5:45:22 AM UTC-4, rrk wrote:
>
> Hi,
>
> Anyone else facing sudden ImportError issues with previously working 
> applications in Python 2.7 runtime of Google App Engine?
>
> One such error is given below, which happens when *requests *package is 
> trying to import *netrc*. This code was working fine until today. 
>
> Traceback (most recent call last):
>
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 240, in Handle
>
> handler = _config_handle.add_wsgi_middleware(self._LoadHandler())
>
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 299, in _LoadHandler
>
> handler, path, err = LoadObject(self._handler)
>
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_lib/versions/1/google/appengine/runtime/wsgi.py",
>  
> line 85, in LoadObject
>
> obj = __import__(path[0])
>
>   File 
> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/x.py",
>  
> line 36, in 
>
> from yy import *
>
>   File "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/
> yy.py", line 32, in 
>
> import requests
>
>   File 
> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/__init__.py",
>  
> line 52, in 
>
> from . import utils
>
>   File 
> "/base/data/home/apps/s~app-id-removed/p31-b.391085029481971487/requests/utils.py",
>  
> line 19, in 
>
> from netrc import netrc, NetrcParseError
>
>   File 
> "/base/data/home/runtimes/python27_experiment/python27_dist/lib/python2.7/netrc.py",
>  
> line 7, in 
>
> import pwd
>
> ImportError: No module named pwd
>
>
> I have the same application deployed for other customers within their 
> accounts and also in my account, but this error seems to have occurred only 
> for one deployment.
>
> Why is this happening? Does this have something to do with the 
> python27_experiment version, which I believe has been in use since over a 
> month (based on error traces on the internet with this version), but this 
> ImportError seems to have got triggered only today? May be my client's 
> application has been included within the experimental version?
>
> Thanks and regards,
> Raj
>

-- 
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/2c623f08-1246-4dac-84e5-b5d21c034206%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error when using google.cloud.logging with logging.v1.RequestLog?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Julian,

I've been able just now to run the same code fine. What might you mean by 
"the type of logging we use on GAE"? Are you doing anything particularly 
odd there?

It's worth mentioning here that this forum isn't meant for technical 
support but rather for general discussion of the platform, services, design 
patterns, etc. This question should have been posted to stackoverflow.com 
on a relevant Cloud Platform / App Engine tag. We monitor Stack Overflow 
regularly, so we'll be able to answer there, although we can perhaps help 
debug this a little here before you move to post there.

Cheers,

Nick
Cloud Platform Community Support

On Monday, March 27, 2017 at 12:25:45 PM UTC-4, Julian Bunn wrote:
>
> Right now we cannot use the request_logs feature for downloading our GAE 
> logs (see my other thread on that problem!), so I thought I would try the 
> newer google.cloud features, and get modern :-)
>
> Here is the simple test I tried:
>
> from google.cloud import logging
> from google.cloud.logging import DESCENDING
> def main():
> client = logging.Client() 
> for entry in client.list_entries(order_by=DESCENDING):
> print entry
> if __name__ == '__main__':
> main()
>
> When executing this (after setting up the gcloud credentials), there seems 
> to be a problem parsing the log entries:
>
> python GetLogsCloud.py
> Traceback (most recent call last):
>   File "GetLogsCloud.py", line 25, in 
> main()
>   File "GetLogsCloud.py", line 18, in main
> for entry in client.list_entries(order_by=DESCENDING):
>   File "c:\python27\lib\site-packages\google\cloud\iterator.py", line 219, 
> in _items_iter
> for item in page:
>   File "c:\python27\lib\site-packages\google\cloud\iterator.py", line 163, 
> in next
> result = self._item_to_value(self._parent, item)
>   File "c:\python27\lib\site-packages\google\cloud\logging\_gax.py", line 
> 488, in _item_to_entry
> resource = MessageToDict(entry_pb)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 133, in MessageToDict
> return printer._MessageToJsonObject(message)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 164, in _MessageToJsonObject
> return self._RegularMessageToJsonObject(message, js)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 196, in _RegularMessageToJsonObject
> js[name] = self._FieldToJsonObject(field, value)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 230, in _FieldToJsonObject
> return self._MessageToJsonObject(value)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 162, in _MessageToJsonObject
> return methodcaller(_WKTJSONMETHODS[full_name][0], message)(self)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 266, in _AnyMessageToJsonObject
> sub_message = _CreateMessageFromTypeUrl(type_url)
>   File "c:\python27\lib\site-packages\google\protobuf\json_format.py", 
> line 341, in _CreateMessageFromTypeUrl
> 'Can not find message descriptor by type_url: {0}.'.format(type_url))
> TypeError: Can not find message descriptor by type_url: 
> type.googleapis.com/google.appengine.logging.v1.RequestLog.
>
> I'm wondering what the issue is here ... is it because of the type of 
> logging we use on GAE?
>
> 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/cd373f85-74d3-4dab-97d7-2693bf1dc6e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Problems with deploying App Engine application

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Augusto,

Which account is signed in with the gcloud tool? Are you sure that account 
has EDITOR privileges on the project? 

Keep in mind that this forum isn't meant for technical support, and ideally 
you should post a question like this to stackoverflow.com, including enough 
details about your situation that someone else could begin to look into the 
issue.  

Cheers,

Nick
Cloud Platform Community Support

On Sunday, March 26, 2017 at 6:09:35 PM UTC-4, Augusto Cadini wrote:
>
> Hi, I have the same error! and I follow your tip but not works! No exists 
> "Cloud Container Build"
>
> Em domingo, 20 de novembro de 2016 22:29:11 UTC-2, Jacquelin Hansel 
> escreveu:
>>
>> Hi everyone,
>>
>> My team and I are working on the Trendy Lights Tutorial 
>>  
>> (connecting App Engine with Earth Engine).
>>
>> We have set up all the files and also have converted the .p12 key to .pem 
>> key but failed to run the app on the Google Cloud Platform and constantly 
>> got the error message saying "You do not have permission to access project 
>> [...] and service "cloudbuilt.googleapis.com" is not for consumer..." 
>> (see attached picture).
>>
>> We have already whitelisted our service account for the use of Earth 
>> Engine. Does anyone know what the problem might be? 
>>
>> Thank you so much!
>>
>> Jacquelin
>>
>

-- 
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/9e6c34e3-4d66-4556-8152-287fe15a1b4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: request_logs GAE authentication stopped working

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Julian,

What version of the SDK are you using? And is this still occurring?

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 24, 2017 at 1:14:26 PM UTC-4, Julian Bunn wrote:
>
> We have a process that uses the request_logs feature to download logs from 
> our GAE app for archival. This has stopped working unexpectedly in the last 
> couple of days, apparently due to an oauth2 authentication issue. I'm not 
> sure if this is a problem at our end, or on the GAE side, and I'm 
> struggling to debug it.
>
> My understanding is that when the oauth2 token has expired, it is 
> refreshed automatically, but that process appears to fail.
>
> Here is what the logs downloader process log shows:
>
> python2.7 request_logs.py
> 2017-03-24 08:55:05,739 INFO root: Recovered sentinel with 
> timestamp: 2017-03-22 09:39:59-07:00
> 08:55 AM Host: appengine.google.com
> 08:55 AM Downloading request logs for app my-gae-service version 4.
> 2017-03-24 08:55:05,757 INFO root: Request with offset None.
> 2017-03-24 08:55:05,757 INFO oauth2client.client: access_token is 
> expired. Now: 2017-03-24 15:55:05.757671, token_expiry: 2017-03-23 23:54:13
> 2017-03-24 08:55:05,757 DEBUGgoogle.appengine.tools.appengine_rpc: 
> _Authenticate skipped auth; needs_auth=False
> 2017-03-24 08:55:05,757 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Sending request to 
> https://appengine.google.com/api/request_logs?app_id=my-gae-service_all=True_vhost=False=1000_header=1=1=4
>  
> headers={'X-appcfg-api-version': '1'} body=
> 2017-03-24 08:55:05,890 DEBUGgoogle.appengine.tools.appengine_rpc: Got 
> http error 401.
> 2017-03-24 08:55:05,890 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Attempting to auth. This is try 1 of 3.
> 2017-03-24 08:55:05,890 INFO oauth2client.client: access_token is 
> expired. Now: 2017-03-24 15:55:05.890322, token_expiry: 2017-03-23 23:54:13
> 2017-03-24 08:55:05,890 DEBUGgoogle.appengine.tools.appengine_rpc: 
> _Authenticate configuring auth; needs_auth=True
> 2017-03-24 08:55:05,890 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Sending request to 
> https://appengine.google.com/api/request_logs?app_id=my-gae-service_all=True_vhost=False=1000_header=1=1=4
>  
> headers={'X-appcfg-api-version': '1'} body=
> 2017-03-24 08:55:05,974 INFO oauth2client.client: Refreshing due to a 
> 401 (attempt 1/2)
> 2017-03-24 08:55:05,975 INFO oauth2client.client: Refreshing 
> access_token
> 2017-03-24 08:55:08,761 DEBUGgoogle.appengine.tools.appengine_rpc: Got 
> http error 500.
> 2017-03-24 08:55:08,761 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Retrying. This is attempt 1 of 3.
> 2017-03-24 08:55:08,761 DEBUGgoogle.appengine.tools.appengine_rpc: 
> _Authenticate configuring auth; needs_auth=True
> 2017-03-24 08:55:08,761 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Sending request to 
> https://appengine.google.com/api/request_logs?app_id=my-gae-service_all=True_vhost=False=1000_header=1=1=4
>  
> headers={'X-appcfg-api-version': '1'} body=
> 2017-03-24 08:55:09,644 DEBUGgoogle.appengine.tools.appengine_rpc: Got 
> http error 500.
> 2017-03-24 08:55:09,644 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Retrying. This is attempt 2 of 3.
> 2017-03-24 08:55:09,644 DEBUGgoogle.appengine.tools.appengine_rpc: 
> _Authenticate configuring auth; needs_auth=True
> 2017-03-24 08:55:09,644 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Sending request to 
> https://appengine.google.com/api/request_logs?app_id=my-gae-service_all=True_vhost=False=1000_header=1=1=4
>  
> headers={'X-appcfg-api-version': '1'} body=
> 2017-03-24 08:55:10,598 DEBUGgoogle.appengine.tools.appengine_rpc: Got 
> http error 500.
> 2017-03-24 08:55:10,598 DEBUGgoogle.appengine.tools.appengine_rpc: 
> Retrying. This is attempt 3 of 3.
> 2017-03-24 08:55:10,598 INFO root: Too many retries for url 
> https://appengine.google.com/api/request_logs?app_id=my-gae-service_all=True_vhost=False=1000_header=1=1=4
> Error 500: --- begin server output ---
>  
>  
> Server Error (500)
>  
> A server error has occurred.
> --- end server output ---
> 2017-03-24 08:55:10,599 INFO root: Downloaded 0 logs
>
> Does anyone have any idea what may be wrong here? 
>
> 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/a99b184d-9f84-4453-89d1-4a516d2cda3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Stanislas,

The exact explanation speculated on in my last post shouldn't be taken as 
any description of what's necessarily going on, however it was an estimate 
of what might be happening based on the logs observed. I'm corresponding 
with experts in this area to get a more clear answer at the moment. 

You could look into deploying on Container Engine 
<https://cloud.google.com/container-engine/>, which would mean that the 
front-end management done by the App Engine Flexible Environment 
infrastructure wouldn't be happening, rather it would be the responsibility 
of the resources you deploy on Container Engine (a managed service based 
pretty transparently on Kubernetes <https://kubernetes.io/>). Surely 
deploying new container images to your pool of instances in a cluster (or 
multiple clusters) would be quite fast, since the master sitting in front 
of your clusters and the nodes in the cluster are not as massively 
distributed as the App Engine Flexible Environment serving infrastructure, 
hence updating their routing rules would be relatively fast. This is 
something to look into and experiment with if you don't want to wait on the 
more detailed word from experts, but don't rush to that if you're not all 
that curious.

I'll get back to this thread with more details when they're forthcoming in 
our investigation.

Cheers,

Nick
Cloud Platform Community Support 

On Tuesday, March 21, 2017 at 3:50:34 PM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> Thanks a lot for the lengthy explanation. 
> In this light, is there anything I can do to speed things up? Like for 
> instance take care of the load-balancer myself? Indeed I don't see a reason 
> why it should need to be changed. Could I do this with GAE or would I have 
> to move to G Container/Compute E?
> Cheers,
>
> On Tue, Mar 21, 2017 at 8:42 PM 'Nick (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Hey Stanislas,
>>
>> My initial hunch was that the issue was the deployment of other resources 
>> necessary to support the containers running. My analysis of 
>> deployment-related logs appears to confirm this:
>>
>> I created a simple NodeJS app using your dockerfile and default.yaml. I 
>> then pushed the docker image to gcr.io and ran "gcloud app deploy 
>> --image-url ..."
>>
>> After about 1 minute of waiting, all resources associated with the 
>> deployment had apparently completed, but the command had not returned yet:
>>
>> ```
>> $ gcloud deployment-manager resources list --deployment 
>> aef-default-20170321t185300
>>
>> NAME   TYPE   
>>   STATE  ERRORS  INTENT
>> aef-default-20170321t185300-00 
>> compute.beta.regionInstanceGroupManager  COMPLETED  []
>> aef-default-20170321t185300-00ahs  compute.v1.httpsHealthCheck   
>>COMPLETED  []
>> aef-default-20170321t185300-00it   compute.v1.instanceTemplate   
>>COMPLETED  []
>> aef-default-20170321t185300-bs compute.v1.backendService 
>>COMPLETED  []
>> aef-default-20170321t185300-hcfw   compute.v1.firewall   
>>COMPLETED  []
>> aef-default-20170321t185300-hcscompute.v1.httpsHealthCheck   
>>COMPLETED  []
>> ```
>>
>> At around the same time that the last of the above completed, I see the 
>> following in the Console logs when selecting the "Deployment" logs source:
>>
>> ```
>> {
>>  protoPayload: {…}
>>  insertId: "54B422B11D921.AE9070D.A80D9821"
>>  resource: {
>>   type: "deployment"
>>   labels: {
>>project_id: ""
>>name: "-gclb"
>>   }
>>  }
>>  timestamp: "2017-03-21T18:54:05.999Z"
>>  severity: "ERROR"
>>  logName: "projects//logs/cloudaudit.googleapis.com
>> %2Factivity"
>> }
>> ```
>>
>> I haven't expanded the protoPayload, but it shows that this was an 
>> attempt to delete the deployment "-gclb" if it exists. It's 
>> near-immediately followed by a log representing an update on the deployment 
>> "-gclb" with createPolicy: "CREATE_OR_ACQUIRE". I believe it's 
>> reasonable to assume gclb stands for "Google Cloud Load Balancer", but I 
>> could be wrong here.
>>
>> About six minutes later, the deployment command finally completed. At 
>> about the same time, the following shows up in the logs:
>>
>> ```
>> 18:59:35.632
>> {"@type":"type.googleapis.com/google.cloud.audit.AuditLog",

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

" at around the same time that the 
command line returned news that the deployment was ready to serve.

This all seems to point to the fact that there are some resources which 
need to be deployed before the app can serve, quite apart from fetching the 
container image from gcr.io. It appears that creating a load balancer / 
updating its rules is an important part of this which naturally will take a 
long time since a whole array of distributed machines in the routing 
infrastructure will need to sign off that they contain the new rules before 
the user can be confident the deployment has completed.

I hope this helps clarify things for you. As we continue to improve the 
infrastructure, doubtless times involved in these steps will decrease. We 
definitely analyze the data related to deployments and all kinds of other 
operations to determine how to streamline our systems. If you ever notice 
something in future that needs explanation, feel free to post in this group 
to inquire.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 21, 2017 at 6:00:11 AM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> My app is based in us-central.
> My app is a very simple nodejs app, that runs an expressjs server. It 
> starts in a few seconds (at most) with the command "node app.js --config 
> config.json"
> I'm attaching my Dockerfile and default.yaml.
> Keep in mind that I deploy using the "gcloud app deploy default.yaml 
> --image-url gcr.io/my-project/default"
> Cheers,
>
> On Mon, Mar 20, 2017 at 9:27 PM 'Nick (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Ah, apologies for sending that last message too quick - I'll also need to 
>> know roughly the details of your application's contents. How long does it 
>> take your code to start up (you can check this by running the container on 
>> your own machine, assuming it has stats comparable to the deployment 
>> machine specs). Along with this information, could you share your 
>> Dockerfile contents with me in response to the email I've just sent you 
>> from esupp...@google.com?
>>
>> Cheers,
>>
>> Nick
>>
>> Cloud Platform Community Support
>>
>> On Saturday, March 18, 2017 at 12:03:46 PM UTC-4, Stanislas Marion wrote:
>>
>>> Hi Nick,
>>> I have tweaked my build so that all the image building is done outside 
>>> of GAE.
>>> After I have pushed my docker image to Google (using gcloud docker -- 
>>> push gcr.io/...) which takes very little time, it seems like the 
>>> "Updating service" step takes forever (7-8min) whereas all that is needed 
>>> is a simple variant of 'docker run new_image' > `migrate traffic to 
>>> new_image'. Why does that last 7-8 minutes ??? Is there any way to speed it 
>>> up? It is very painful when developing.
>>> Best,
>>>
>>> On Monday, October 3, 2016 at 10:39:50 PM UTC+2, Nick (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> Hey Kevin,
>>>>
>>>> The speed of deployment can be changed by limiting the size of the 
>>>> uploaded app, limiting the complexity of the build necessary in the 
>>>> Dockerfile, if present, and by ensuring a fast and reliable internet 
>>>> connection. Other than these variables, it's hard to comment on what 
>>>> specifically might be making deployment exhibit the timing that it does on 
>>>> your system. 
>>>>
>>>> I hope this is helpful - let me know if you have any further questions! 
>>>> I'll be happy to help!
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Suppor
>>>>
>>>> On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>>>>>
>>>>>
>>>>> Is there a faster way to deploy an app? Google App Engine is slow to 
>>>>> deploy, hangs on "Updating service [someproject]..." I am using a 
>>>>> flexible 
>>>>> environment with PHP.
>>>>>
>>>>
>>> *"This email and any files transmitted with it are confidential and 
>>> intended solely for the use of the individual or entity to whom they are 
>>> addressed. If you have received this email in error please notify the 
>>> sender immediately"*
>>>
>> -- 
>> 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/to

Re: [google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Stanislas,

Thanks for the information. I'll see what I can find out about this and 
will report back here.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, March 21, 2017 at 6:00:11 AM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> My app is based in us-central.
> My app is a very simple nodejs app, that runs an expressjs server. It 
> starts in a few seconds (at most) with the command "node app.js --config 
> config.json"
> I'm attaching my Dockerfile and default.yaml.
> Keep in mind that I deploy using the "gcloud app deploy default.yaml 
> --image-url gcr.io/my-project/default"
> Cheers,
>
> On Mon, Mar 20, 2017 at 9:27 PM 'Nick (Cloud Platform Support)' via Google 
> App Engine <google-appengine@googlegroups.com> wrote:
>
>> Ah, apologies for sending that last message too quick - I'll also need to 
>> know roughly the details of your application's contents. How long does it 
>> take your code to start up (you can check this by running the container on 
>> your own machine, assuming it has stats comparable to the deployment 
>> machine specs). Along with this information, could you share your 
>> Dockerfile contents with me in response to the email I've just sent you 
>> from esupp...@google.com?
>>
>> Cheers,
>>
>> Nick
>>
>> Cloud Platform Community Support
>>
>> On Saturday, March 18, 2017 at 12:03:46 PM UTC-4, Stanislas Marion wrote:
>>
>>> Hi Nick,
>>> I have tweaked my build so that all the image building is done outside 
>>> of GAE.
>>> After I have pushed my docker image to Google (using gcloud docker -- 
>>> push gcr.io/...) which takes very little time, it seems like the 
>>> "Updating service" step takes forever (7-8min) whereas all that is needed 
>>> is a simple variant of 'docker run new_image' > `migrate traffic to 
>>> new_image'. Why does that last 7-8 minutes ??? Is there any way to speed it 
>>> up? It is very painful when developing.
>>> Best,
>>>
>>> On Monday, October 3, 2016 at 10:39:50 PM UTC+2, Nick (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> Hey Kevin,
>>>>
>>>> The speed of deployment can be changed by limiting the size of the 
>>>> uploaded app, limiting the complexity of the build necessary in the 
>>>> Dockerfile, if present, and by ensuring a fast and reliable internet 
>>>> connection. Other than these variables, it's hard to comment on what 
>>>> specifically might be making deployment exhibit the timing that it does on 
>>>> your system. 
>>>>
>>>> I hope this is helpful - let me know if you have any further questions! 
>>>> I'll be happy to help!
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Suppor
>>>>
>>>> On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>>>>>
>>>>>
>>>>> Is there a faster way to deploy an app? Google App Engine is slow to 
>>>>> deploy, hangs on "Updating service [someproject]..." I am using a 
>>>>> flexible 
>>>>> environment with PHP.
>>>>>
>>>>
>>> *"This email and any files transmitted with it are confidential and 
>>> intended solely for the use of the individual or entity to whom they are 
>>> addressed. If you have received this email in error please notify the 
>>> sender immediately"*
>>>
>> -- 
>> 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/hZMEkmmObDU/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 https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/5aa7088c-a33e-4135-974b-232adc1c4c08%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/5aa7088c-a33e-4135-974b-232adc1c4c08%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> *"This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they are 
> addressed. If you have received this email in error please notify the 
> sender immediately"*
>

-- 
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/c2343454-2459-4f1b-b9f2-a9296bc9ca37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Ah, apologies for sending that last message too quick - I'll also need to 
know roughly the details of your application's contents. How long does it 
take your code to start up (you can check this by running the container on 
your own machine, assuming it has stats comparable to the deployment 
machine specs). Along with this information, could you share your 
Dockerfile contents with me in response to the email I've just sent you 
from esupp...@google.com?

Cheers,

Nick
Cloud Platform Community Support

On Saturday, March 18, 2017 at 12:03:46 PM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> I have tweaked my build so that all the image building is done outside of 
> GAE.
> After I have pushed my docker image to Google (using gcloud docker -- push 
> gcr.io/...) which takes very little time, it seems like the "Updating 
> service" step takes forever (7-8min) whereas all that is needed is a simple 
> variant of 'docker run new_image' > `migrate traffic to new_image'. Why 
> does that last 7-8 minutes ??? Is there any way to speed it up? It is very 
> painful when developing.
> Best,
>
> On Monday, October 3, 2016 at 10:39:50 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Kevin,
>>
>> The speed of deployment can be changed by limiting the size of the 
>> uploaded app, limiting the complexity of the build necessary in the 
>> Dockerfile, if present, and by ensuring a fast and reliable internet 
>> connection. Other than these variables, it's hard to comment on what 
>> specifically might be making deployment exhibit the timing that it does on 
>> your system. 
>>
>> I hope this is helpful - let me know if you have any further questions! 
>> I'll be happy to help!
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Suppor
>>
>> On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>>>
>>>
>>> Is there a faster way to deploy an app? Google App Engine is slow to 
>>> deploy, hangs on "Updating service [someproject]..." I am using a flexible 
>>> environment with PHP.
>>>
>>
> *"This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they are 
> addressed. If you have received this email in error please notify the 
> sender immediately"*
>

-- 
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/5aa7088c-a33e-4135-974b-232adc1c4c08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine is slow to deploy, hangs on "Updating service [someproject]..."

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Stanislas,

Could you let me know which region your app is based in? I'll attempt to 
reproduce this behaviour and hope to either have a reply explaining a bit 
of what's going on or else I can file a Public Issue Tracker 
<http://issuetracker.google.com> issue for you to follow as a Feature 
Request on improving deployment times.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, March 18, 2017 at 12:03:46 PM UTC-4, Stanislas Marion wrote:
>
> Hi Nick,
> I have tweaked my build so that all the image building is done outside of 
> GAE.
> After I have pushed my docker image to Google (using gcloud docker -- push 
> gcr.io/...) which takes very little time, it seems like the "Updating 
> service" step takes forever (7-8min) whereas all that is needed is a simple 
> variant of 'docker run new_image' > `migrate traffic to new_image'. Why 
> does that last 7-8 minutes ??? Is there any way to speed it up? It is very 
> painful when developing.
> Best,
>
> On Monday, October 3, 2016 at 10:39:50 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Kevin,
>>
>> The speed of deployment can be changed by limiting the size of the 
>> uploaded app, limiting the complexity of the build necessary in the 
>> Dockerfile, if present, and by ensuring a fast and reliable internet 
>> connection. Other than these variables, it's hard to comment on what 
>> specifically might be making deployment exhibit the timing that it does on 
>> your system. 
>>
>> I hope this is helpful - let me know if you have any further questions! 
>> I'll be happy to help!
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Suppor
>>
>> On Thursday, September 29, 2016 at 3:48:26 PM UTC-4, Kevin Lau wrote:
>>>
>>>
>>> Is there a faster way to deploy an app? Google App Engine is slow to 
>>> deploy, hangs on "Updating service [someproject]..." I am using a flexible 
>>> environment with PHP.
>>>
>>
> *"This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they are 
> addressed. If you have received this email in error please notify the 
> sender immediately"*
>

-- 
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/5104dbbb-3dbc-4e4e-a6da-5f3b7212a3df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 502 server error

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Teofilus,

This forum isn't meant for specific technical issues, and should be used 
for more high level and general discussion about the platform, services, 
design patterns, etc. If you'd like assistance with a technical issue, 
please post to Stack Overflow  on an appropriate 
tag (google-app-engine 
 perhaps). We 
monitor Stack Overflow regularly and you'll find a much larger community of 
users there to assist you.

Now before you go, I do have some advice:

First, have you tried searching online for other users who have seen an 
issue like this? Usually you won't be the first person to see an issue and 
the work of others can be leveraged to find solutions more quickly. 

Second, you should post more details when reporting a technical issue, such 
as: 

* what kind of app you deployed
* any relevant configuration file details
* what logs you had specifically checked
* confirmation that you set the log viewer levels correctly to capture all 
logs and/or all logs sources
* how long it's been since you deployed the app
* whether the issue recurs repeatedly or just occasionally


These sort of details will help the users on Stack Overflow to begin 
working on understanding what might have caused your issue.

Once you post there, feel free to provide a link here - I'll be happy to 
jump on the thread there and assist!

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 17, 2017 at 3:07:09 PM UTC-4, Teofilus Candra wrote:
>
> My google appengine show 
> "Error: Server ErrorThe server encountered a temporary error and could 
> not complete your request.Please try again in 30 seconds.
> " when page opened..
>
> But no error in log and when i push new code, it will always say "internal 
> server error"
> Anyone can help?
>

-- 
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/9d9e7d9b-505b-4443-9373-e6870da99103%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine Standard - Instance charges

['Nick (Cloud Platform Support)' via Google App Engine]

Hey George,

Unfortunately as I'm not involved in Billing Support I have no knowledge of 
your case with them. I can only advise that you explain to them clearly the 
way in which you believe your app's observed behaviour has differed from 
our SLA's <https://cloud.google.com/appengine/sla> or our Pricing 
documentation <https://cloud.google.com/appengine/pricing>, and they should 
be able to help you out in whatever way possible based on that.

Cheers,

Nick
Cloud Platform Community Support 

On Monday, March 13, 2017 at 9:50:13 PM UTC-4, Lawrence Mok wrote:
>
> Hi Nick I have exactly the same issues, dealing with the junior billing 
> staff has been very frustrating and they are unable to acknowledge the 
> problem at all.
>
> I hope your team should take this issue seriously as my billing is going 
> sky rocket (something like 10X times more than the normal level).
>
> Please also see the other guy and my screen shots in the other thread:
> https://groups.google.com/forum/#!topic/google-appengine/X6sWwvUGbzQ
>
>
> On Tuesday, March 14, 2017 at 4:43:59 AM UTC+8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey George,
>>
>> I recommend opening a ticket with Billing 
>> <https://support.google.com/cloud/contact/cloud_platform_billing> to 
>> resolve this, as you'll surely get a specific response, while this forum is 
>> intended less for specific-issue one-on-one technical support and is 
>> instead meant to be a forum where users discuss the platform, services, 
>> design patterns, etc.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Monday, March 13, 2017 at 3:49:49 PM UTC-4, George Bittmann wrote:
>>>
>>> Thanks for the suggestion Karolína. All of these projects have had 
>>> min_idle_instances at default and have been that way since they were 
>>> created most are at least 6 months with the current configuration and 
>>> incurring no charges.
>>>
>>> Billing indicates the charges are front end hours, but if you look at 
>>> appengine > quotas > usage history every day shows 0 charges for the month.
>>>
>>> I'm thinking that for some period of time, a couple days perhaps, our 
>>> projects were charged as if the free 28 frontend hours did not exist. The 
>>> amount of hours billed does seem generally related to the traffic of the 
>>> site, but as I said these sites are extremely low traffic and would on a 
>>> very busy day would not reach 20 frontend hours.
>>>
>>>
>>>
>>> On Monday, March 13, 2017 at 3:29:29 PM UTC-4, Karolína Netolická wrote:
>>>>
>>>> Hi George, one thing I can think of is that if you are using 
>>>> min_idle_instances setting, this could be causing apps with low traffic to 
>>>> incur a bill. For free apps we recommend setting min_idle_instances to 
>>>> zero.
>>>>
>>>> On Monday, March 13, 2017 at 9:32:38 AM UTC-7, George Bittmann wrote:
>>>>>
>>>>> Did anything change recently with how the standard environment is 
>>>>> billed? 
>>>>>
>>>>> I'm seeing charges on a lot of projects that are hosting extremely low 
>>>>> traffic websites that should never incur instance charges at all let 
>>>>> alone 
>>>>> getting up over a dollar or two half way into the month.
>>>>>
>>>>> Has anyone else seen this or know what might be going on?
>>>>>
>>>>>
>>>>>

-- 
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/65d31fa2-f479-4db8-9eb0-1bc9d20aff41%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine Standard - Instance charges

['Nick (Cloud Platform Support)' via Google App Engine]

Hey George,

I recommend opening a ticket with Billing 
 to 
resolve this, as you'll surely get a specific response, while this forum is 
intended less for specific-issue one-on-one technical support and is 
instead meant to be a forum where users discuss the platform, services, 
design patterns, etc.

Cheers,

Nick
Cloud Platform Community Support

On Monday, March 13, 2017 at 3:49:49 PM UTC-4, George Bittmann wrote:
>
> Thanks for the suggestion Karolína. All of these projects have had 
> min_idle_instances at default and have been that way since they were 
> created most are at least 6 months with the current configuration and 
> incurring no charges.
>
> Billing indicates the charges are front end hours, but if you look at 
> appengine > quotas > usage history every day shows 0 charges for the month.
>
> I'm thinking that for some period of time, a couple days perhaps, our 
> projects were charged as if the free 28 frontend hours did not exist. The 
> amount of hours billed does seem generally related to the traffic of the 
> site, but as I said these sites are extremely low traffic and would on a 
> very busy day would not reach 20 frontend hours.
>
>
>
> On Monday, March 13, 2017 at 3:29:29 PM UTC-4, Karolína Netolická wrote:
>>
>> Hi George, one thing I can think of is that if you are using 
>> min_idle_instances setting, this could be causing apps with low traffic to 
>> incur a bill. For free apps we recommend setting min_idle_instances to zero.
>>
>> On Monday, March 13, 2017 at 9:32:38 AM UTC-7, George Bittmann wrote:
>>>
>>> Did anything change recently with how the standard environment is 
>>> billed? 
>>>
>>> I'm seeing charges on a lot of projects that are hosting extremely low 
>>> traffic websites that should never incur instance charges at all let alone 
>>> getting up over a dollar or two half way into the month.
>>>
>>> Has anyone else seen this or know what might be going on?
>>>
>>>
>>>

-- 
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/ff437b04-78b6-474f-9eff-5d51949f2bc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: MemCache and NDB

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Ivo,

The qualification for a hot key is a key that receives over 100 QPS in the 
memcache, as our docs say [1]. You have had a few hot keys over the course 
of the past few days, from our investigation. These ought to have been 
displayed. We've taken note of this and created an internal issue to track 
work on it. You can follow this public issue [2] for updates.

Cheers,

Nick
Cloud Platform Community Support

[1] 
https://cloud.google.com/appengine/docs/standard/java/memcache/using#monitoring_memcache
[2] https://issuetracker.google.com/36103562

On Friday, March 3, 2017 at 6:00:20 AM UTC-5, Ivo Bellin Salarin wrote:
>
> Hi all,
>
> I have two questions concerning memcache and its performances.
>
> I was reading the page 
> https://cloud.google.com/appengine/articles/best-practices-for-app-engine-memcache#distribute_load_across_the_keyspace,
>  
> where I found
> *The Memcache viewer in the administration console displays a list of top 
> keys, which can be used to identify bottlenecks*
>
> In my administration console, this section is empty. (i.e. 'No hot keys')
> But yes, I am sure that there are hot keys, since among the stackdriver 
> insights I can see the following messages
> Slow memcache calls. Your app made 1 remote procedure calls to memcache 
> that took more than 50 ms and the slowest call took 66 ms. Consider 
> reducing the value of max_concurrent_requests for your app.
> 1) Thus, where can I find the hottest keys of my dedicated memcache?
>
> In the meanwhile, according to the messages I can find in StackDriver, the 
> longest (thus, probably, hottest) memcache.get(s) are made by ndb.get(). In 
> the code of ndb.get I can see that the cache keys are **not** distributed 
> across the keyspace (as recommended by the page above).
> I think that not using memcache (use_memcache=False) would be a worse 
> solution.
> 2) Is there a way to force a better key distribution for NDB, apart from 
> monkey patching 
> /gcloud/platform/google_appengine/google/appengine/ext/ndb/context.py::Context._memcache_prefix
>  
> with a time dependent % operation? :-)
>

-- 
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/555801c2-75f1-47c9-8470-a9df33520f2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 10mib request limit being hit with call to sendgrid api - Is there another way to make the sendgrid api call with attachments?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Rob, 

Thanks for clarifying. The 10 MB UrlFetch request size limit is a hard 
limit on the service. In this case, I'd recommend using Cloud Storage to 
serve the files you want to send, as mentioned in my last reply. 

Cheers,

Nick
Cloud Platform Community

On Sunday, March 5, 2017 at 11:07:29 PM UTC-5, Rob Curtis wrote:
>
> Hi Nick,
>
> Thanks for you response. Sorry I missed this.
>
> What I meant is that the* google urlfetch limit is 10MB* limit on request 
> size, and because we have send the entire message (to sendgrid) as json 
> with B64 encoded files, we can only send a maximum of 10MB (which is the 
> limit imposted by GAE). 
>
> I wanted to know if there is any method to relax the 10MB limit imposed by 
> GAE?
>
> Thanks
> Rob
>
>
>
> On Wednesday, March 1, 2017 at 9:10:42 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Rob,
>>
>> The attachment size limit for the Mail API can't be relaxed. Sendgrid's 
>> limit is larger, at 30MB 
>> <https://sendgrid.com/docs/Classroom/Build/Add_Content/attachments.html>, 
>> but I'm unsure what you mean in your post. Do you mean to say that files, 
>> when b64 encoded, will be larger than *30 *MB (the sendgrid limit)?
>>
>> One way you can get around this entirely (and solutions like this are 
>> becoming more and more popular as cloud storage becomes cheaper and 
>> cheaper) is to store the items in Cloud Storage 
>> <https://cloud.google.com/storage/> and send an email to your user with 
>> a Signed URL 
>> <https://cloud.google.com/storage/docs/access-control/signed-urls> for 
>> downloading it, or add their email to the ACL 
>> <https://cloud.google.com/storage/docs/access-control/lists> on the 
>> object / bucket and serve them a simple URL like storage.googleapis.com/
>> **/* *(read more on such URL's here 
>> <https://cloud.google.com/storage/docs/request-endpoints>).
>>
>> Let me know if you have any further questions and I'll be happy to assist.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, February 28, 2017 at 10:22:11 AM UTC-5, Rob Curtis wrote:
>>>
>>> Hi, 
>>>
>>> We have an application where a list attachments must be sent in a single 
>>> mail to 1 address. 
>>> Sendgrid has 30MB limit on attachment size, but Appengine has a 10MB 
>>> limit on request size.
>>> The sendgrid api requires base64 encoding of the files, which results in 
>>> the request size being larger than 10MB (if the files are large)
>>>
>>>
>>>1. Is there an alternative method for attaching files to a mail in 
>>>sendgrid?
>>>2. Is there means to change the request size in AppEngine or use 
>>>some mechanism for calling the sendgrid API?
>>>
>>> Thanks
>>> Rob
>>>
>>

-- 
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/d25750ba-d8ff-43bf-87f8-59c4583a5a72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Need help: I can't shutdown app engine version. Keeps billing.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Marco, 

I'm glad to hear you got in touch with Billing Support. If you've got any 
further questions, feel free to comment in this thread, but it seems things 
should go smoothly from here on out with Billing Support.

Cheers!

Nick
Cloud Platform Community Support

On Wednesday, March 8, 2017 at 3:45:49 AM UTC-5, Marco Galassi wrote:
>
> Hi Nick,
> I understand, and in fact as soon as I was pointed out that I immediately 
> report this issue at the Billing Support.
> At the time I wrote this I had a wrong thought that even that support was 
> only allowed to premium support users,
> so I was searching for help in the communities.
> Thank you very much for your help.
>
> Marco
>
>
> On Tuesday, March 7, 2017 at 10:50:47 PM UTC+1, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Marco,
>>
>> This forum is for general and high level discussion of the platform and 
>> services that many users can contribute to, being more of a discussion 
>> forum than an issue-reporting forum. Unfortunately, the majority of users 
>> don't know this so it has the appearance of the latter. So, we're 
>> understanding when a user makes a post like this which is better directed 
>> to another forum. In your case, Stack Exchange was a better forum, but also 
>> isn't quite suited for that forum. As I commented on both your Stack Q's, 
>> this should have been posted either to the Issue Tracker 
>> <http://issuetracker.google.com> or directly to Billing 
>> <https://support.google.com/cloud/contact/cloud_platform_billing>.
>>
>> Best of luck!
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, March 7, 2017 at 10:02:30 AM UTC-5, Marco Galassi wrote:
>>>
>>> I am not able to stop and consequently delete a app engine version.
>>> I have 3 different versions at the moment, under the same default 
>>> service:
>>>
>>>1.  gappa-v1, which is currently serving 100% of the traffic
>>>2.  mg-v1, which is currently stopped
>>>3.  20170223t163224
>>>
>>>
>>> I am able to stop, restart and delete all the versions but the 
>>> 20170223t163224 version.
>>> I have tried everything, both from the Google Cloud Console, and the 
>>> gcloud command-line tool.
>>> Interacting from the Google Cloud Console is kinda useless because it 
>>> gives me no feedback on the error, but just a generic *Failed to stop 
>>> version* on 
>>> a stop attemp or a generic *The version could not be deleted* on a 
>>> delete attempt.
>>>
>>> When interacting with the gcloud command line tool, I have tried:
>>>
>>> *$> *gcloud app versions stop 20170223t163224
>>> *$>* ERROR: (gcloud.app.versions.stop) INTERNAL: This flexible 
>>> version cannot be modified, it can only be deleted.
>>>
>>> Then if I try to delete it:
>>>
>>> *$>* gcloud app versions delete `20170223t163224`
>>> *$>* [default/20170223t163224]: Error Response: [13] Deployment 
>>> Manager operation failed, name: 
>>> operation-1488895382516-54a247861f121-d456a139-0b1e3fc6, error: 
>>> [{"code":"RESOURCE_ERROR","locati
>>> 
>>> on":"/deployments/aef-default-20170223t163224/resources/aef-default-20170223t163224-00","message":"{\"ResourceType\":\"compute.beta.regionInstanceGroupManager\",\"ResourceErrorCode\":\"400
>>> 
>>> \",\"ResourceErrorMessage\":{\"code\":400,\"errors\":[{\"domain\":\"global\",\"message\":\"The
>>>  
>>> instance_group_manager resource 'aef-default-20170223t163224-00' is already 
>>> being used by 'ae
>>> 
>>> f-default-20170223t163224'\",\"reason\":\"resourceInUseByAnotherResource\"}],\"message\":\"The
>>>  
>>> instance_group_manager resource 'aef-default-20170223t163224-00' is already 
>>> being used by 'ae
>>> f-default-20170223t163224'\",\"statusMessage\":\"Bad 
>>> Request\",\"requestPath\":\"
>>> https://www.googleapis.com/compute/beta/projects/MYAPPID/regions/us-central1/instanceGroupMana
>>> gers/aef-default-20170223t163224-00\"}}"}]
>>>
>>> Somewhere (I can't find where in this moment), the docs says I can't 
>>> delete a version until traffic is allocated to it.  So, I made sure 
>>> that the version has no

[google-appengine] Re: Need help: I can't shutdown app engine version. Keeps billing.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Marco,

This forum is for general and high level discussion of the platform and 
services that many users can contribute to, being more of a discussion 
forum than an issue-reporting forum. Unfortunately, the majority of users 
don't know this so it has the appearance of the latter. So, we're 
understanding when a user makes a post like this which is better directed 
to another forum. In your case, Stack Exchange was a better forum, but also 
isn't quite suited for that forum. As I commented on both your Stack Q's, 
this should have been posted either to the Issue Tracker 
 or directly to Billing 
.

Best of luck!

Nick
Cloud Platform Community Support

On Tuesday, March 7, 2017 at 10:02:30 AM UTC-5, Marco Galassi wrote:
>
> I am not able to stop and consequently delete a app engine version.
> I have 3 different versions at the moment, under the same default service:
>
>1.  gappa-v1, which is currently serving 100% of the traffic
>2.  mg-v1, which is currently stopped
>3.  20170223t163224
>
>
> I am able to stop, restart and delete all the versions but the 
> 20170223t163224 version.
> I have tried everything, both from the Google Cloud Console, and the 
> gcloud command-line tool.
> Interacting from the Google Cloud Console is kinda useless because it 
> gives me no feedback on the error, but just a generic *Failed to stop 
> version* on 
> a stop attemp or a generic *The version could not be deleted* on a delete 
> attempt.
>
> When interacting with the gcloud command line tool, I have tried:
>
> *$> *gcloud app versions stop 20170223t163224
> *$>* ERROR: (gcloud.app.versions.stop) INTERNAL: This flexible 
> version cannot be modified, it can only be deleted.
>
> Then if I try to delete it:
>
> *$>* gcloud app versions delete `20170223t163224`
> *$>* [default/20170223t163224]: Error Response: [13] Deployment 
> Manager operation failed, name: 
> operation-1488895382516-54a247861f121-d456a139-0b1e3fc6, error: 
> [{"code":"RESOURCE_ERROR","locati
> 
> on":"/deployments/aef-default-20170223t163224/resources/aef-default-20170223t163224-00","message":"{\"ResourceType\":\"compute.beta.regionInstanceGroupManager\",\"ResourceErrorCode\":\"400
> 
> \",\"ResourceErrorMessage\":{\"code\":400,\"errors\":[{\"domain\":\"global\",\"message\":\"The
>  
> instance_group_manager resource 'aef-default-20170223t163224-00' is already 
> being used by 'ae
> 
> f-default-20170223t163224'\",\"reason\":\"resourceInUseByAnotherResource\"}],\"message\":\"The
>  
> instance_group_manager resource 'aef-default-20170223t163224-00' is already 
> being used by 'ae
> f-default-20170223t163224'\",\"statusMessage\":\"Bad 
> Request\",\"requestPath\":\"
> https://www.googleapis.com/compute/beta/projects/MYAPPID/regions/us-central1/instanceGroupMana
> gers/aef-default-20170223t163224-00\"}}"}]
>
> Somewhere (I can't find where in this moment), the docs says I can't 
> delete a version until traffic is allocated to it.  So, I made sure 
> that the version has no traffic allocated. Infact the app engine console 
> shows the following:
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
> I have also tried to delete the single version instances using gcloud app 
> instances delete INSTANCE_ID --service=default --version=20170223t163224.
> This command didn't return any error, but had no effect, there are still 2 
> instances for version 20170223t163224.
>
> I also tried to override the version deploying a new, basically empty app 
> (hello world, from the google tutorial 
> ), but it 
> didn't allow me to deploy it.
> *The biggest problem* is that i am still getting charged for this 
> version, as the version is still there, serving using 2 instances.
>
> I have also posted this to Stackoverflow 
> 
>  and Serverfault 
> 
> .
>
> I am currently working with Google App Engine Flexible Environment and 
> NodeJS.
>
> Thank you very much.
>

-- 
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/bdf7c0bb-3984-4fb3-b015-f270c17371a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine multiple regions

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Pavelescu,

The page you link, "Creating Cross-Region Load Balancing", from our docs, 
is relevant for Compute Engine instances, rather than App Engine. While App 
Engine Flexible Environment apps run on Compute Engine VM's, they deploy 
only to the same region that you select for your App Engine app when 
creating it, hence there's no possibility of cross-region load balancing 
for Flexible Environment apps either. This may change in the future (as 
anything could, I suppose), but I can't provide a guarantee of course. Feel 
free to file Feature Requests for any features you desire on our Issue 
Tracker <http://issuetracker.google.com>.

Cheers,

Nick
Cloud Platform Community Support

On Sunday, March 5, 2017 at 11:12:22 AM UTC-5, Pavelescu Razvan wrote:
>
> Hello Tom,
>
> I've just came across this section in the gcloud documentation: 
> https://cloud.google.com/compute/docs/load-balancing/http/cross-region-example
>
> Isn't this exactly what Yon tried to achieve?
>
> Thanks,
> Razvan
>
> marți, 21 iunie 2016, 15:17:59 UTC+3, Tom Walder a scris:
>>
>> You cannot load balance between US and EU using "conventional" load 
>> balancing.
>>
>> There might be some thoroughly complex way to do it with localised DNS 
>> responses.
>>
>> However, it would be 2 distinct App Engine projects.
>>
>> To be honest if cross-region load balancing is a need, App Engine is 
>> probably not the right solution. Look at Compute engine instead.
>>
>> Tom
>>
>>
>>
>>
>> On Tuesday, 21 June 2016 06:36:26 UTC+1, Yon Dev wrote:
>>>
>>> Hello Nick,
>>>
>>> Thank you for your answer.
>>>
>>> I might be misunderstanding something so please correct me if I am wrong.
>>>
>>> I can only upload 1 app engine instance per project. So if I want to 
>>> deploy to both the US and EU I will have to create 2 different projects. 
>>> And if I were to create multiple projects, how should I handle my custom 
>>> domain?
>>>
>>> To have a single domain I believe I have to use a load balancer, but I 
>>> thought the HTTP load balancer was only available when using Compute Engine 
>>> and not for App Engine?
>>> And if I were to have to have 2 separate projects I don't think it's 
>>> possible to do load balancing between them, right?
>>>
>>> Sincerely,
>>> Yon
>>>
>>> Den tisdag 21 juni 2016 kl. 03:16:11 UTC+9 skrev Nick (Cloud Platform 
>>> Support):
>>>>
>>>> Hey Yon,
>>>>
>>>> App Engine instances are scaled in zones within the region the 
>>>> application is created in 
>>>> <https://cloud.google.com/appengine/docs/python/console/#create>. If 
>>>> you'd like to follow a pattern which others have made use of, you can 
>>>> deploy another project in the EU to handle traffic there. As you point 
>>>> out, 
>>>> an HTTP Load Balancer is a very useful in this situation, and you can use 
>>>> Container 
>>>> Engine <https://cloud.google.com/container-engine/> to deploy Docker 
>>>> images of your applications, using Custom Runtimes 
>>>> <https://cloud.google.com/appengine/docs/flexible/custom-runtimes/>.
>>>>
>>>> I hope this has helped answer your question. Let me know if you have 
>>>> any further questions, and I'll be happy to assist.
>>>>
>>>> Sincerely,
>>>>
>>>> Nick
>>>> Cloud Platform Community Support
>>>>
>>>> On Monday, June 20, 2016 at 5:13:12 AM UTC-4, Yon Dev wrote:
>>>>>
>>>>> I am evaluating whether GAE would be a good fit for an upcoming 
>>>>> project.
>>>>>
>>>>> I was wondering how scaling across regions work with GAE? If I set my 
>>>>> project location to US and then create an GAE instance and most access to 
>>>>> the GAE is from EU will it automatically scale out to Europe? 
>>>>> Or how does it work?
>>>>> If it was a on Compute Engine I believe I could have created multiple 
>>>>> instances and then made a HTTP Load Balancer that would route the user to 
>>>>> the closest instance based on proximity.
>>>>>
>>>>> https://cloud.google.com/about/locations/
>>>>> Reading the link above it says that it scales automatically within or 
>>>>> accross multi-regional locations.
>>>>> What does that mean? Do I have to ena

[google-appengine] Re: MemCache and NDB

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Ivo,

It seems odd that you'd see nothing for hot keys. I've emailed you to ask 
for your project ID, so feel free to reply to that email when you get a 
chance. 

In the meantime, I'm also curious about your observation of the key 
distribution. Could you possibly show some sample keys, 
sanitized/obfuscated for security, but which will still give an indication 
of what you mean by the key space not being properly distributed-into by 
NDB? If you like, you can also include the keys, without alteration, in 
your private email reply.

Of course, feel free to add any other useful information or any additional 
questions.

Cheers,

Nick
Cloud Platform Community Support

On Friday, March 3, 2017 at 6:00:20 AM UTC-5, Ivo Bellin Salarin wrote:
>
> Hi all,
>
> I have two questions concerning memcache and its performances.
>
> I was reading the page 
> https://cloud.google.com/appengine/articles/best-practices-for-app-engine-memcache#distribute_load_across_the_keyspace,
>  
> where I found
> *The Memcache viewer in the administration console displays a list of top 
> keys, which can be used to identify bottlenecks*
>
> In my administration console, this section is empty. (i.e. 'No hot keys')
> But yes, I am sure that there are hot keys, since among the stackdriver 
> insights I can see the following messages
> Slow memcache calls. Your app made 1 remote procedure calls to memcache 
> that took more than 50 ms and the slowest call took 66 ms. Consider 
> reducing the value of max_concurrent_requests for your app.
> 1) Thus, where can I find the hottest keys of my dedicated memcache?
>
> In the meanwhile, according to the messages I can find in StackDriver, the 
> longest (thus, probably, hottest) memcache.get(s) are made by ndb.get(). In 
> the code of ndb.get I can see that the cache keys are **not** distributed 
> across the keyspace (as recommended by the page above).
> I think that not using memcache (use_memcache=False) would be a worse 
> solution.
> 2) Is there a way to force a better key distribution for NDB, apart from 
> monkey patching 
> /gcloud/platform/google_appengine/google/appengine/ext/ndb/context.py::Context._memcache_prefix
>  
> with a time dependent % operation? :-)
>

-- 
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/9dabb18d-8ad8-4a2e-8c1d-9679e1aa5afe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine Flex "Error: Server Error" occurs often, how to find cause?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Nickolas,

This forum should be used to post general discussion threads about the 
platform, services, design patterns, etc., and a specific-issue question 
like this should be posted to Stack Overflow, although maybe we could 
gather more information before that, as in this state it seems there's not 
quite enough information for anyone to begin working on it. I have some 
lines of investigation which might lead to a better understanding:

1 .This could be a case of not inspecting the logs with the right logs 
level - are you sure you're viewing "All logs", and not just "stdout, 
stderr"? 



2. You might also want to check whether you have any logs for the resource 
"Cloud HTTP Load Balancer" as opposed to "GAE Application" 

3. A final thing to check would be the headers attached to the response - 
specifically looking to see what the "server" header says - to determine 
whether this response is generated by our machines or your own. It seems to 
look like an error that our infrastructure generates, not your app, but 
it's good to check.

Let me know what you find, and feel free to ask any further questions or 
provide any information you think may be relevant.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 2, 2017 at 7:19:16 PM UTC-5, Nickolas Daskalou wrote:
>
> Hi,
>
> If we hit our Flexible environment service (Python 3 runtime) with a 
> relatively low concurrency level using ApacheBench, we get this returned 
> more often than not:
>
> Error: Server ErrorThe server encountered a temporary error and could not 
> complete your request.
>
> Please try again in 30 seconds.
>
> I can't seem to find any information in any of logs about why this is 
> occurring.
>
> Is there a way to get the cause of the above page being returned, whether 
> it be via the logs or otherwise?
>
> Thanks,
> Nick
>

-- 
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/a944a61c-c6bd-4022-841f-9fabe5ae9bf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore String length limit of 1,500 bytes when using JDO

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Jim,

Do I understand correctly that you only see the issue when you attempt to 
index the field - or what's the same thing - it doesn't occur when you turn 
the field's indexing off? 

Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 2, 2017 at 1:26:02 PM UTC-5, Jim wrote:
>
> When I attempt to write a Datastore string longer than 1,500 bytes via JDO 
> I get the following error:   "String properties must be 1500 bytes or less. 
>  Instead, use com.google.appengine.api.datastore.Text, which can store 
> strings of any length."
>
> I've annotated my class to turn indexing off on this field, and I can 
> manually insert strings (much) longer than 1,500 bytes manually via the 
> Datastore Console.  
>
> Is there any way to store larger String values via JDO?  It seems like an 
> arbitrary limitation given the fact that I can manually insert larger 
> values into the Datastore, and Datastore doc says Strings can be up to ~1MB 
> in size.  I know I can convert these to Text but I'd rather not do that if 
> I can avoid it.
>

-- 
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/0775243c-61b1-4a9a-b1ab-fcc14e33ea0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE PHP - Vulnerability patching strategy?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Tommie,

As usual, we can't speak on any specific timeline for the Flexible 
Environment going from Beta into General Availability. It definitely 
depends on what work remains to be done, any unexpected technical problems 
to solve, etc. As for the PHP runtime and CVE's, I've forwarded this 
question to some colleagues who work directly with the PHP runtime and we 
hope to have a more authoritative answer shortly.

Cheers,

Nick
Cloud Platform Community Support 

On Thursday, March 2, 2017 at 9:01:35 AM UTC-5, Tommie wrote:
>
> Hi Nick,
>
> Thanks for getting back to us.
>
> Our main concern is that current PHP-version is so far behind the current 
> "state the art", especially since the current version on AppEngine is from 
> 31 Mar 2016. Which means that we're slowly crawling up on one full year 
> without any updates. Which is a hard sell to my customers which i intend to 
> move over to AppEngine. 
>
> While the flexible environment is interesting and look very versatile, 
> it's difficult to consider that as an option as long as Google themself 
> does not recommend it for production use.
>
> Do you have any timeline for the PHP upgrades or when the flexible 
> environment is expected to go out of beta?
>
> Thanks,
> Tommie
>
> On Wednesday, March 1, 2017 at 9:35:04 PM UTC+1, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Tommie,
>>
>> Just as an update on this topic, I'll give you an idea of what we might 
>> consider adding to the documentation page directly to explain our process:
>>
>> Google takes security and the robustness of our products seriously. Each 
>> new version of PHP is tested as a completely new runtime. In order to 
>> ensure the environments are secure and durable, extensive testing and 
>> development is required. 
>>
>>
>> In general, the App Engine team is aware of the desire of the latest 
>> version runtime. As mentioned, it's currently possible to implement a 
>> custom runtime[1] on App Engine Flex containing the desired runtime.
>>
>> [1] - https://cloud.google.com/appengine/docs/flexible/custom-runtimes/
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>>
>> On Friday, February 24, 2017 at 9:13:24 AM UTC-5, Tommie wrote:
>>>
>>> Official docs says PHP is on version 5.5.34. Most recent security update 
>>> is 5.5.38.
>>>
>>> On Friday, February 24, 2017 at 3:11:15 PM UTC+1, Tommie wrote:
>>>>
>>>> Hi,
>>>>
>>>> Does anyone know where to find vulnerability patching strategies and/or 
>>>> official documentation on how google keeps its PHP version patched from 
>>>> new 
>>>> CVEs? I'm investigating GAE for a project and i'm finding very little 
>>>> documentation around this. 
>>>>
>>>> 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/5d9688fe-bf19-4671-8e17-fb4c653a0dd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Stackdriver Trace] Cannot have multiple spans with the same name in a trace

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adrian,

We've reproduced this issue and you can track progress on it here in the 
google-cloud-platform  Public Issue Tracker 
<https://code.google.com/p/google-cloud-platform/issues/detail?id=243>.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, February 28, 2017 at 9:11:22 AM UTC-5, Nick (Cloud Platform 
Support) wrote:
>
> Hey Adrian,
>
> Not to worry, I ought to have updated here to let you know - we're working 
> on diagnosing the issue and preparing an internal report for it, and will 
> post a public issue tracker thread and link it here once we've got that 
> squared away. Shouldn't be too much longer. Thanks for checking! In future, 
> you can post directly there, but it's no problem for us to create a thread 
> this way in this case.
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, February 28, 2017 at 9:06:24 AM UTC-5, Adrian Bogatu wrote:
>>
>> Are there any updates regarding this issue? Do you want me to post it 
>> directly to Google Code?
>>
>> On Friday, February 24, 2017 at 5:51:28 PM UTC+2, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Adrian,
>>>
>>> While opening new projects on Google Code was discontinued, we continue 
>>> to operate Public Issue Trackers for many of our projects there as the 
>>> official forums for issue reporting, and we monitor them daily. Here are a 
>>> few of them:
>>>
>>> App Engine <https://code.google.com/p/googleappengine/issues/list>
>>> Compute Engine 
>>> <https://code.google.com/p/google-compute-engine/issues/list>
>>> Cloud SDK <https://code.google.com/p/google-cloud-sdk/issues/list>
>>> Cloud SQL <https://code.google.com/p/googlecloudsql/issues/list>
>>> BigQuery <https://code.google.com/p/google-bigquery/issues/list>
>>> Cloud Platform 
>>> <https://code.google.com/p/google-cloud-platform/issues/list>
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Friday, February 24, 2017 at 4:05:05 AM UTC-5, Adrian Bogatu wrote:
>>>>
>>>> Hi, Nick,
>>>>
>>>> Thanks for the answer. Honestly, at first, I wanted to post on Google 
>>>> Code, but I know it has been discontinued in 2016 and I wasn't sure it was 
>>>> tracked anymore.
>>>>
>>>> Thanks,
>>>> Adrian
>>>>
>>>> On Thursday, February 23, 2017 at 10:16:04 PM UTC+2, Nick (Cloud 
>>>> Platform Support) wrote:
>>>>>
>>>>> Hey Adrian,
>>>>>
>>>>> Thanks for reporting this. I've just about reproduced this behaviour 
>>>>> and will shortly post a link to a Public Issue Tracker 
>>>>> <https://code.google.com/p/google-cloud-platform/issues/list> thread 
>>>>> you can follow for updates. 
>>>>>
>>>>> In general, posts like this, which look like a post that belongs in 
>>>>> the Public Issue Tracker, should be posted there. This Google Groups 
>>>>> forum 
>>>>> is meant for more general and high level discussion of the App Engine 
>>>>> platform and services rather than specific-issue technical reporting. We 
>>>>> monitor there regularly and will quickly get the issue acknowledged and 
>>>>> tracked.
>>>>>
>>>>> I'll update this thread with a link to the thread once it's made, or 
>>>>> if I need any further clarification on reproducing this behaviour.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Nick
>>>>> Cloud Platform Community Support
>>>>>
>>>>> On Thursday, February 23, 2017 at 11:13:27 AM UTC-5, Adrian Bogatu 
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Situation: When sending a trace containing 2 spans (a root-span and a 
>>>>>> child span) that have the same span name, the two spans are merged 
>>>>>> together 
>>>>>> and only one span is displayed. In addition, some of the fields are 
>>>>>> overwritten and information is lost.
>>>>>>
>>>>>> See example in the attachment (print screen from developer console in 
>>>>>> google cloud platform), where two spans both having the name "get_test" 
>>>>>> are 
>>>>>> sent in a trace to Stackdriver Trace:

[google-appengine] Re: GAE PHP - Vulnerability patching strategy?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Tommie,

Just as an update on this topic, I'll give you an idea of what we might 
consider adding to the documentation page directly to explain our process:

Google takes security and the robustness of our products seriously. Each 
new version of PHP is tested as a completely new runtime. In order to 
ensure the environments are secure and durable, extensive testing and 
development is required. 


In general, the App Engine team is aware of the desire of the latest 
version runtime. As mentioned, it's currently possible to implement a 
custom runtime[1] on App Engine Flex containing the desired runtime.

[1] - https://cloud.google.com/appengine/docs/flexible/custom-runtimes/

Cheers,

Nick
Cloud Platform Community Support


On Friday, February 24, 2017 at 9:13:24 AM UTC-5, Tommie wrote:
>
> Official docs says PHP is on version 5.5.34. Most recent security update 
> is 5.5.38.
>
> On Friday, February 24, 2017 at 3:11:15 PM UTC+1, Tommie wrote:
>>
>> Hi,
>>
>> Does anyone know where to find vulnerability patching strategies and/or 
>> official documentation on how google keeps its PHP version patched from new 
>> CVEs? I'm investigating GAE for a project and i'm finding very little 
>> documentation around this. 
>>
>> 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/c7898a9c-e483-4495-8fcb-9a96ecde7304%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 10mib request limit being hit with call to sendgrid api - Is there another way to make the sendgrid api call with attachments?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Rob,

The attachment size limit for the Mail API can't be relaxed. Sendgrid's 
limit is larger, at 30MB 
, 
but I'm unsure what you mean in your post. Do you mean to say that files, 
when b64 encoded, will be larger than *30 *MB (the sendgrid limit)?

One way you can get around this entirely (and solutions like this are 
becoming more and more popular as cloud storage becomes cheaper and 
cheaper) is to store the items in Cloud Storage 
 and send an email to your user with a 
Signed 
URL  for 
downloading it, or add their email to the ACL 
 on the object 
/ bucket and serve them a simple URL like storage.googleapis.com/**/
* *(read more on such URL's here 
).

Let me know if you have any further questions and I'll be happy to assist.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, February 28, 2017 at 10:22:11 AM UTC-5, Rob Curtis wrote:
>
> Hi, 
>
> We have an application where a list attachments must be sent in a single 
> mail to 1 address. 
> Sendgrid has 30MB limit on attachment size, but Appengine has a 10MB limit 
> on request size.
> The sendgrid api requires base64 encoding of the files, which results in 
> the request size being larger than 10MB (if the files are large)
>
>
>1. Is there an alternative method for attaching files to a mail in 
>sendgrid?
>2. Is there means to change the request size in AppEngine or use some 
>mechanism for calling the sendgrid API?
>
> Thanks
> Rob
>

-- 
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/2bfa2dea-aed5-431d-89eb-05f141473a96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to use the same G. Cloud Datastore for apps in standard and flexible environments?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Juan,

You're right to point out that our documentation could be better here. 
We're currently working on expanding the documentation on the Datastore 
emulator. Now, as to your main question:

*google-cloud-datastore*

You can use the google-cloud-datastore 
 library to interact 
with the datastore emulator from both standard and flexible environment 
dev_appserver apps. 

*environment variables*

Just be sure to set the environment variables properly by running $(gcloud 
beta emulators datastore env-init). Be sure to run the command exactly like 
that, with the $() included, since this will tell the shell to run the 
commands which are actually output by gcloud beta emulators datastore 
env-init. The commands, which you could also examine and then run yourself, 
one by one, are going to look like this:

export DATASTORE_DATASET=my-project-id
export DATASTORE_EMULATOR_HOST=localhost:8715
export DATASTORE_EMULATOR_HOST_PATH=localhost:8715/datastore
export DATASTORE_HOST=http://localhost:8715
export DATASTORE_PROJECT_ID=my-project-id

*and you're good to go*

When this is done, the python client library linked above will connect to 
the local emulator. See the documentation on the client library (the link 
was above) for the details of coding.

*a small note about the datastore admin viewer in dev*

Currently, the dev_appserver.py admin panel (localhost:8000 usually) 
"datastore" section does not connect properly to the emulator. This is 
documented in this Public Issue Tracker issue I've just filed 
, and you 
can star that issue to receive updates. I hope this has been helpful to 
you, and feel free to ask any further questions you have. I'll be happy to 
assist.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 16, 2017 at 7:59:32 AM UTC-5, Juan Antonio Fernández 
Sánchez wrote:
>
> I'm working in a project that use two apps, one deployed in App Engine 
> standard environment and other in flexible env.
>
>
> One service of the app in the standard env and the app in the flex env. 
> must be access to Google Cloud Datastore 
> .
>
> If I use in *local* the emulated datastore that run the dev_server in 
> standard environment, the app in the flex env. can't access to this 
> datastore and neither use the ndb ORM library like the service in standard 
> env.
>
>
> So, to have consistency in the way to access to data, I don't what 
> solution would be better to solve this.
>
> I've been thinking if I could use Google Cloud SDK (gcloud tool) to run 
> emulators 
> datastore and access to this using Cloud Datastore Cient Libraries 
>  ( instead 
> of Google Datastore NDB Client Library 
>  ) in both apps (to 
> use exactly the same way to connect) I think that this way is most easy to 
> develop after in cloud platform.
>
>
> I'm finding some problems to connect with this emulated datastore and I 
> would like to know if my approach is good to follow fighting with the 
> problems or change to another way or idea to run my entire project in local.
>
>
> Any help or idea will be welcome.
>

-- 
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/f6d1ef7f-5329-41bd-906a-7048b1163e3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Stackdriver Trace] Cannot have multiple spans with the same name in a trace

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adrian,

Not to worry, I ought to have updated here to let you know - we're working 
on diagnosing the issue and preparing an internal report for it, and will 
post a public issue tracker thread and link it here once we've got that 
squared away. Shouldn't be too much longer. Thanks for checking! In future, 
you can post directly there, but it's no problem for us to create a thread 
this way in this case.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, February 28, 2017 at 9:06:24 AM UTC-5, Adrian Bogatu wrote:
>
> Are there any updates regarding this issue? Do you want me to post it 
> directly to Google Code?
>
> On Friday, February 24, 2017 at 5:51:28 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Adrian,
>>
>> While opening new projects on Google Code was discontinued, we continue 
>> to operate Public Issue Trackers for many of our projects there as the 
>> official forums for issue reporting, and we monitor them daily. Here are a 
>> few of them:
>>
>> App Engine <https://code.google.com/p/googleappengine/issues/list>
>> Compute Engine 
>> <https://code.google.com/p/google-compute-engine/issues/list>
>> Cloud SDK <https://code.google.com/p/google-cloud-sdk/issues/list>
>> Cloud SQL <https://code.google.com/p/googlecloudsql/issues/list>
>> BigQuery <https://code.google.com/p/google-bigquery/issues/list>
>> Cloud Platform 
>> <https://code.google.com/p/google-cloud-platform/issues/list>
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Friday, February 24, 2017 at 4:05:05 AM UTC-5, Adrian Bogatu wrote:
>>>
>>> Hi, Nick,
>>>
>>> Thanks for the answer. Honestly, at first, I wanted to post on Google 
>>> Code, but I know it has been discontinued in 2016 and I wasn't sure it was 
>>> tracked anymore.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> On Thursday, February 23, 2017 at 10:16:04 PM UTC+2, Nick (Cloud 
>>> Platform Support) wrote:
>>>>
>>>> Hey Adrian,
>>>>
>>>> Thanks for reporting this. I've just about reproduced this behaviour 
>>>> and will shortly post a link to a Public Issue Tracker 
>>>> <https://code.google.com/p/google-cloud-platform/issues/list> thread 
>>>> you can follow for updates. 
>>>>
>>>> In general, posts like this, which look like a post that belongs in the 
>>>> Public Issue Tracker, should be posted there. This Google Groups forum is 
>>>> meant for more general and high level discussion of the App Engine 
>>>> platform 
>>>> and services rather than specific-issue technical reporting. We monitor 
>>>> there regularly and will quickly get the issue acknowledged and tracked.
>>>>
>>>> I'll update this thread with a link to the thread once it's made, or if 
>>>> I need any further clarification on reproducing this behaviour.
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Support
>>>>
>>>> On Thursday, February 23, 2017 at 11:13:27 AM UTC-5, Adrian Bogatu 
>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Situation: When sending a trace containing 2 spans (a root-span and a 
>>>>> child span) that have the same span name, the two spans are merged 
>>>>> together 
>>>>> and only one span is displayed. In addition, some of the fields are 
>>>>> overwritten and information is lost.
>>>>>
>>>>> See example in the attachment (print screen from developer console in 
>>>>> google cloud platform), where two spans both having the name "get_test" 
>>>>> are 
>>>>> sent in a trace to Stackdriver Trace: one client root-span and one server 
>>>>> child span. The different annotations of both the spans are merged, but 
>>>>> some shared annotations are overwritten by the client root-span (e.g. 
>>>>> zipkin.io/span.kind is "client"). I expected to have 2 spans: one 
>>>>> with the tag-value "client" and one "server".
>>>>>
>>>>> This issue is because, I am guessing, the backend considers the span's 
>>>>> uniqueness based on the span's name. I don't think that's correct, 
>>>>> instead 
>>>>> the unique *span id* should be used to track spans.
>>>>>
>>>&g

[google-appengine] Re: Which library for Non linear Conjugate Gradient on GAE for python?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Sumanta,

It's correct to say that the App Engine Standard Environment 
 for python 
doesn't support modules based on C code. just go head and write the non-linear 
CG algorithm 
 in pure 
python and attempt to run it, but there are two things to keep in mind:

* It seems you'd have to write it. I searched a bit and couldn't find any 
pre-made code for this.

* scipy / numpy will be much faster.

I recommend you either offload these computation problems to a Compute 
Engine  instance (possibly of micro 
instance class) or deploy an App Engine Flexible Environment 
 app where the 
Dockerfile  uses pip 
 to install your requirements.txt 
, containing the 
dependencies, so that when the app is deployed, you have numpy and scipy. 

You can also find sample apps 

 
which install numpy and scipy in our github "python-docs-samples" repo 
(they're under "scipy" and "numpy").

Cheers,

Nick
Cloud Platform Community Support

On Sunday, February 26, 2017 at 11:42:08 AM UTC-5, Sumanta Bhowmik wrote:
>
>  I do not want to write a Non linear CG implementation on my own. As far 
> as I know, GAE(python) supports numpy but does not support scipy(which has 
> optimization). I did not come across a pure python implementation on the 
> net. But I am sure many people would have had similar requirements. Is 
> there some library that I can use on GAE?
>

-- 
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/737d12bc-fc4c-4b73-bda5-0f12bd984f5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: OAuth2 server-to-server on Google App Engine

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Joshua,

You correctly found that you can use service account credentials from a 
keyfile. You can also use Application Default Credentials 
,
 
which will give access to anything that your app's default service account 
can access. This is good for many API's.

Cheers,

Nick
Cloud Platform Community Support

On Friday, February 24, 2017 at 3:42:06 PM UTC-5, Joshua Smith wrote:
>
> Nevermind. I found this:
>
> https://developers.google.com/identity/protocols/OAuth2ServiceAccount
>
> The code is pretty simple:
>
> class GetGAHandler(webapp2.RequestHandler):
>   def get(self):
> from oauth2client.service_account import ServiceAccountCredentials
> from httplib2 import Http
> from apiclient.discovery import build
> credentials = ServiceAccountCredentials.from_json_keyfile_name(
>   CLIENT_SECRETS, scopes=['
> https://www.googleapis.com/auth/analytics.readonly'])
> http_auth = credentials.authorize(Http())
> service = build("analytics", "v3", http=http_auth)
>
> Getting the google-api-python-client installed in a local folder was a 
> nightmare, and convincing GAE to use it wasn’t obvious. However, once I 
> sorted through all that, the above code works like a champ.
>
> On Feb 24, 2017, at 1:27 PM, Joshua Smith  
> wrote:
>
> I’m trying to access the Google Analytics API from a Google App Engine 
> app. I got this working a long time ago, before Analytics was one of the 
> APIs you could use server-to-server.
>
> So I have code that works with an administrator user in the middle of the 
> transaction. I used the decorator from oauth2client.appengine import 
> oauth2decorator_from_clientsecrets
>
> What I’d like to do is get this working so my google app engine app 
> (written in Python) can just talk to google analytics without a person in 
> the loop. I can’t find an example of that.
>
> Since all the google services seem to work the same way, I probably don’t 
> need an example of connecting to analytics. Rather, just an example of how 
> to connect to any google service without a user in the middle would be 
> great.
>
> The following code doesn’t work, but hopefully will give you an idea of 
> what I’m trying to do. It is failing because there’s no callback set up.
>
> class StorageDuck():
>  def put(self, content):
>console.log("Pretending to put: "+content)
>
> class GetGAHandler(webapp2.RequestHandler):
>  def get(self):
>from apiclient.discovery import build
>from oauth2client import client
>from oauth2client import file
>from oauth2client import tools
>http = httplib2.Http(memcache)
>service = build("analytics", "v3", http=http)
>flow = client.flow_from_clientsecrets(
>  CLIENT_SECRETS,
>  scope='https://www.googleapis.com/auth/analytics.readonly',
>  message="")
>credentials = tools.run(flow, StorageDuck())
>chttp = credentials.authorize(http=httplib2.Http())
>
> Any pointers?
>
> -Joshua
>
>
>

-- 
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/01e750ff-51dc-45c3-af4c-f4df380a00cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE PHP - Vulnerability patching strategy?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Tommie,

You're right that it appears our docs don't have an explicit page dealing 
with this question. Perhaps we could write one, and I'll see about getting 
this request tracked, although I can't guarantee it will occur. 

At any rate, the latest update is 5.6.30 
, which means that even 5.5.38 is many 
CVE's behind the "state of the art". In order to use a latest-version PHP 
server, you'll have to administer your own PHP server on Compute Engine 
 or deploy a Custom Runtime 
 
app on the App Engine Flexible Environment 
.

I'll let you know if I have any more useful information to share about the 
process of selecting the PHP version used in the App Engine production 
environment.

Cheers,

Nick
Cloud Platform Community Support

On Friday, February 24, 2017 at 9:13:24 AM UTC-5, Tommie wrote:
>
> Official docs says PHP is on version 5.5.34. Most recent security update 
> is 5.5.38.
>
> On Friday, February 24, 2017 at 3:11:15 PM UTC+1, Tommie wrote:
>>
>> Hi,
>>
>> Does anyone know where to find vulnerability patching strategies and/or 
>> official documentation on how google keeps its PHP version patched from new 
>> CVEs? I'm investigating GAE for a project and i'm finding very little 
>> documentation around this. 
>>
>> 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/90909df3-ce2a-4000-ba23-05daa52838ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Working with unicode filenames on cloudstorage?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Attila,

Through testing, I've determined that in fact the pattern urllib.quote 
(unicodestr.encode ('utf-8')) does in fact work. Have you seen this on your 
end? I've attached to this post an example project which illustrates the 
use. Send it a request like so to see it at work:

curl -v localhost:8080/?method=enc-url

I hope this is helpful in at least comparing what I've done with your case. 
Let me know if the url-encoding method doesn't work. This is the proper way 
to send utf-8 data in a URL, to encode it and URL quote it (resulting in 
the URL encoding of the bytes. In my case, the string u'☸' is encoded to '
%E2%98%B8').

Cheers,

Nick
Cloud Platform Community Support

On Monday, February 13, 2017 at 9:04:38 AM UTC-5, Attila-Mihaly Balazs 
wrote:
>
> Hello,
>
> I'm trying to create / delete files on google cloudstorage with unicode 
> characters in the name. GCS seems to support this alright, however the 
> client APIs seem to have problems.
>
> - Environment: Google Appengine Standard with Python 2.7. Tested locally 
> with dev_server 1.9.50. The library used (both locally and in production) 
> is the latest GoogleAppEngineCloudStorageClient [1] (1.9.22.1)
>
> - Some code snippets:
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(fn, 'w') as f_out: f_out.write('old')
>
> This gets me the traceback at [2]
>
> - Ok, how about manually encoding it?
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(fn.encode('utf-8'), 'w') as f_out: f_out.write('old')
>
> This just gets me several retries until the request is aborted [3]
>
> - There is the option of encoding it, however I don't believe this is 
> correct (this is just double quoting the filename):
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(urllib.quote(fn.encode('utf-8')), 'w') as f_out: 
> f_out.write('old')
>
> - I believe gcs.delete is also affected since I have the following 
> traceback in production [4]
>
> How are unicode filenames supposed to be used with the cloudstorage 
> library? Also, is the cloudstorage library supposed to be used at all? 
> Looking around I found the google-cloud-storage library on PyPi (
> https://pypi.python.org/pypi/google-cloud-storage) which also seems to be 
> an official Google project and perhaps has better support for unicode?
>
> Attila 
>
> [1] https://pypi.python.org/pypi/GoogleAppEngineCloudStorageClient
> [2] Traceback with u'...'
> /usr/local/google_appengine_1.9.50/google/appengine/dist27/urllib.py:1277: 
> UnicodeWarning: Unicode equal comparison failed to convert both arguments 
> to Unicode - interpreting them as being unequal
>   return ''.join(map(quoter, s))
> ERROR2017-02-13 13:52:30,401 webapp2.py:1552] u'\xe1'
> Traceback (most recent call last):
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1535, in __call__
> rv = self.handle_exception(request, response, e)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1529, in __call__
> rv = self.router.dispatch(request, response)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1278, in default_dispatcher
> return route.handler_adapter(request, response)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1102, in __call__
> return handler.dispatch()
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 572, in dispatch
> return self.handle_exception(e, self.app.debug)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 570, in dispatch
> return method(*args, **kwargs)
>   File "/tmp/gcs_test_unicode_names/main.py", line 14, in get
> with gcs.open(fn, 'w') as f_out: f_out.write('old')
>   File "/tmp/gcs_test_unicode_names/lib/cloudstorage/cloudstorage_api.py", 
> line 91, in open
> filename = api_utils._quote_filename(filename)
>   File "/tmp/gcs_test_unicode_names/lib/cloudstorage/api_utils.py", line 
> 94, in _quote_filename
> return urllib.quote(filename)
>   File 
> "/usr/local/google_appengine_1.9.50/google/appengine/dist27/urllib.py", 
> line 1277, in quote
> return ''.join(map(quoter, s))
> KeyError: u'\xe1'
> 
> [3] Traceback with manually encoded filename
> ---
> ERROR2017-02-13 13:53:44,679 module.py:892] Request to 
> '/_ah/gcs/app_default_bucket/\xc3\xa1' failed
> INFO 2017-02-13 13:53:44,680 module.py:806] default: "POST 
> /_ah/gcs/app_default_bucket/%C3%A1 HTTP/1.1" 500 -
> ERROR2017-02-13 13:53:44,790 module.py:892] Request to 
> '/_ah/gcs/app_default_bucket/\xc3\xa1' failed
> INFO 2017-02-13 13:53:44,791 module.py:806] default: "POST 
> /_ah/gcs/app_default_bucket/%C3%A1 HTTP/1.1" 500 -
> ERROR2017-02-13 13:53:45,003 module.py:892] Request to 
> '/_ah/gcs/app_default_bucket/\xc3\xa1' failed
> INFO 2017-02-13 13:53:45,004 module.py:806] default: "POST 
> /_ah/gcs/app_default_bucket/%C3%A1 HTTP/1.1" 500 -
> ERROR

[google-appengine] Re: [Stackdriver Trace] Cannot have multiple spans with the same name in a trace

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adrian,

While opening new projects on Google Code was discontinued, we continue to 
operate Public Issue Trackers for many of our projects there as the 
official forums for issue reporting, and we monitor them daily. Here are a 
few of them:

App Engine <https://code.google.com/p/googleappengine/issues/list>
Compute Engine <https://code.google.com/p/google-compute-engine/issues/list>
Cloud SDK <https://code.google.com/p/google-cloud-sdk/issues/list>
Cloud SQL <https://code.google.com/p/googlecloudsql/issues/list>
BigQuery <https://code.google.com/p/google-bigquery/issues/list>
Cloud Platform <https://code.google.com/p/google-cloud-platform/issues/list>

Cheers,

Nick
Cloud Platform Community Support

On Friday, February 24, 2017 at 4:05:05 AM UTC-5, Adrian Bogatu wrote:
>
> Hi, Nick,
>
> Thanks for the answer. Honestly, at first, I wanted to post on Google 
> Code, but I know it has been discontinued in 2016 and I wasn't sure it was 
> tracked anymore.
>
> Thanks,
> Adrian
>
> On Thursday, February 23, 2017 at 10:16:04 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Adrian,
>>
>> Thanks for reporting this. I've just about reproduced this behaviour and 
>> will shortly post a link to a Public Issue Tracker 
>> <https://code.google.com/p/google-cloud-platform/issues/list> thread you 
>> can follow for updates. 
>>
>> In general, posts like this, which look like a post that belongs in the 
>> Public Issue Tracker, should be posted there. This Google Groups forum is 
>> meant for more general and high level discussion of the App Engine platform 
>> and services rather than specific-issue technical reporting. We monitor 
>> there regularly and will quickly get the issue acknowledged and tracked.
>>
>> I'll update this thread with a link to the thread once it's made, or if I 
>> need any further clarification on reproducing this behaviour.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, February 23, 2017 at 11:13:27 AM UTC-5, Adrian Bogatu wrote:
>>>
>>> Hi,
>>>
>>> Situation: When sending a trace containing 2 spans (a root-span and a 
>>> child span) that have the same span name, the two spans are merged together 
>>> and only one span is displayed. In addition, some of the fields are 
>>> overwritten and information is lost.
>>>
>>> See example in the attachment (print screen from developer console in 
>>> google cloud platform), where two spans both having the name "get_test" are 
>>> sent in a trace to Stackdriver Trace: one client root-span and one server 
>>> child span. The different annotations of both the spans are merged, but 
>>> some shared annotations are overwritten by the client root-span (e.g. 
>>> zipkin.io/span.kind is "client"). I expected to have 2 spans: one with 
>>> the tag-value "client" and one "server".
>>>
>>> This issue is because, I am guessing, the backend considers the span's 
>>> uniqueness based on the span's name. I don't think that's correct, instead 
>>> the unique *span id* should be used to track spans.
>>>
>>> There are many cases when one wants to use the same name for multiple 
>>> spans in a trace (e.g. span_name="get_users" to be the same for client and 
>>> server; standard annotations in libraries like span_name="mysql-client" 
>>> when you have multiple sequential MySQL request). In those cases, only one 
>>> span with that specified name will exist, and annotations will be lost.
>>>
>>> I used both a custom stackdriver trace client in Go (that uses Go 
>>> package cloudtrace/v1 
>>> <https://github.com/google/google-api-go-client/tree/master/cloudtrace>) 
>>> and the relatively new google's zipkin collector for stackdriver trace 
>>> <https://github.com/GoogleCloudPlatform/stackdriver-zipkin>.
>>>
>>> Thanks,
>>> Adrian
>>>
>>

-- 
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/f9180343-5073-46a1-8896-667631b7da19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [Stackdriver Trace] Cannot have multiple spans with the same name in a trace

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adrian,

Thanks for reporting this. I've just about reproduced this behaviour and 
will shortly post a link to a Public Issue Tracker 
 thread you 
can follow for updates. 

In general, posts like this, which look like a post that belongs in the 
Public Issue Tracker, should be posted there. This Google Groups forum is 
meant for more general and high level discussion of the App Engine platform 
and services rather than specific-issue technical reporting. We monitor 
there regularly and will quickly get the issue acknowledged and tracked.

I'll update this thread with a link to the thread once it's made, or if I 
need any further clarification on reproducing this behaviour.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 23, 2017 at 11:13:27 AM UTC-5, Adrian Bogatu wrote:
>
> Hi,
>
> Situation: When sending a trace containing 2 spans (a root-span and a 
> child span) that have the same span name, the two spans are merged together 
> and only one span is displayed. In addition, some of the fields are 
> overwritten and information is lost.
>
> See example in the attachment (print screen from developer console in 
> google cloud platform), where two spans both having the name "get_test" are 
> sent in a trace to Stackdriver Trace: one client root-span and one server 
> child span. The different annotations of both the spans are merged, but 
> some shared annotations are overwritten by the client root-span (e.g. 
> zipkin.io/span.kind is "client"). I expected to have 2 spans: one with 
> the tag-value "client" and one "server".
>
> This issue is because, I am guessing, the backend considers the span's 
> uniqueness based on the span's name. I don't think that's correct, instead 
> the unique *span id* should be used to track spans.
>
> There are many cases when one wants to use the same name for multiple 
> spans in a trace (e.g. span_name="get_users" to be the same for client and 
> server; standard annotations in libraries like span_name="mysql-client" 
> when you have multiple sequential MySQL request). In those cases, only one 
> span with that specified name will exist, and annotations will be lost.
>
> I used both a custom stackdriver trace client in Go (that uses Go package 
> cloudtrace/v1 
> ) 
> and the relatively new google's zipkin collector for stackdriver trace 
> .
>
> Thanks,
> Adrian
>

-- 
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/054c5d38-60ac-437e-9636-bff1ae0f80af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Custom domain SSL issue

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Rodrigo,

It appears this is expected behaviour as Startcom root certificates are 
distrusted by Google and Chrome. See this Google Security Blog post 
 
for 
details.

So, it seems you should get a new root certificate authority. Let me know 
if you have any further questions!

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, February 22, 2017 at 9:16:03 AM UTC-5, Rodrigo Ferreira wrote:
>
> Can someone help me figure out what is wrong with this SSL certificate 
> installation on GAE?
>
>
> upholdex.tk
>
>
> I get a net::ERR_CERT_AUTHORITY_INVALID error on Chrome and a 
> SEC_ERROR_REVOKED_CERTIFICATE on Firefox.
>
>
> The certificates were issued by StartSLL.
>
>
> I have tested the installation with multiple online SSL checking tools, 
> all seem fine. The only one that hints a problem is 
> https://www.htbridge.com/ssl/ where I get "Server sends an unnecessary 
> root certificate.", but I tried removing the root certificate from the 
> chain and the problem persists.
>
>
> A similar setup of a different domain with the same certificate chain 
> works fine on AWS+Nginx. It makes me think that this is something related 
> to GAE. Maybe the StartSSL root certificate has been revoked on GAE? Does 
> this make sense? I have made many deployments of SSL installations but I am 
> far from an expert.
>
>
>

-- 
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/5bf89a10-2a6c-4e38-b2bd-55be3f0c9664%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoint API not working properly via API Explorer after deployment to App Engine Standard

['Nick (Cloud Platform Support)' via Google App Engine]

Hey George,

Thanks for clarifying that. Any future users reading this thread will 
surely find your responses to be clear and hopefully of use in their own 
case. Yes, it's indeed the case (see the docs article "Using Firebase and 
App Engine Standard Environment in an Android App - Configuring the App 
Engine backend to use manual scaling" 
<https://cloud.google.com/solutions/mobile/firebase-app-engine-android-studio#configuring_the_app_engine_backend_to_use_manual_scaling>)
 
that you need to run manual scaling on the service in your app that handles 
connections to Firebase.

Cheers,

Nick
Cloud Platform Community Support

On Monday, February 20, 2017 at 4:33:19 PM UTC-5, George Sxi wrote:
>
> Hi Nick ,
>
> Sorry for the delayed reply...been diving in the depths of app engine for 
> a while...heh..
>
> Well in my case I had to include the following lines in my 
> appengine-web.xml in the android studio :
>
>  
>  1
>  
>
>
> my understanding is (and please correct me if I am wrong) that in order to 
> use Firebase with App Engine standard environment, manual instance scaling 
> must be used because Firebase needs long lived background threads to listen 
> and such threads are allowed only on manually scaled instances..
> After including this I finally got results to my tests directly from 
> Firebase Database.
> Let me know if my understanding is correct..
>
> Thanks,
> George
>
>
>
> On Monday, February 13, 2017 at 10:33:44 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey George,
>>
>> That's great to hear. Keep in mind that we also monitor our tags on Stack 
>> Overflow, so I'll be there as well if you ask a question, haha. Glad to 
>> have been of assistance.
>>
>> One last question I have, though, is what you meant about manual scaling. 
>> Could you share some more information about that? How was manual scaling 
>> involved in this issue's appearance / solution?
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Saturday, February 11, 2017 at 4:14:37 AM UTC-5, George Sxi wrote:
>>>
>>> Many thanks for your insight Nick, in my case, apart from the issue you 
>>> described I have also forgotten to include "manual scaling" in the relevant 
>>> .xml which was causing the issue.
>>>  
>>> Let me point out that your reply was the fastest and most accurate from 
>>> any of my stack overflow posts :) 
>>> Will keep in mind to try there first though. 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/afe433b2-9fcb-40de-93a3-6640fb18382f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: deploy is very slow

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Alex,

Slow deploys can be caused by many factors. If you want to submit a Public 
Issue Tracker <https://code.google.com/p/googleappengine/issues/list> issue 
for us to look at, you should consider including the following information:

1. The size on disk of your project
2. Whether you're using the flexible environment or not, and whether you 
have a Dockerfile (if so, the contents of the Dockerfile)
3. The number of files in the project
4. The deploy log stored in a location given by running gcloud info and 
seeing the "Last Log File" field.

With this information we'll be able to better understand whether the deploy 
time is expected or exceptional.

Cheers,

Nick
Cloud Platform Community Support

On Monday, February 20, 2017 at 11:19:58 AM UTC-5, Alex Komoroske wrote:
>
> I'm running into this too with the Go flexible environment. Deploys are 
> taking 30+ minutes.
>
> On Monday, February 13, 2017 at 12:44:20 PM UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Luis, 
>>
>> The best way in fact would be to create a Public Issue Tracker 
>> <https://code.google.com/p/google-cloud-platform/issues/list>thread, and 
>> we'll be able to follow up there. Post the link here once you've created a 
>> thread, and I'll be happy to assist, sending you an email which you can 
>> reply to, attaching the log. 
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Sunday, February 12, 2017 at 11:57:14 AM UTC-5, Luis F De Pombo wrote:
>>>
>>> Hi Nick,
>>> I am having the same issue as Adam but I am using a nodejs Flex env. I 
>>> have the file you point to, what is the best email to get this to you? 
>>> Thank you.
>>>
>>> On Monday, February 6, 2017 at 10:40:48 AM UTC-8, Nick (Cloud Platform 
>>> Support) wrote:
>>>>
>>>> Just a quick update:
>>>>
>>>> As well, to avoid the timestamp filtering commands above, you could 
>>>> simply run the deployment with the --verbosity debug and --log-http flags 
>>>> and then run gcloud info to check for where the "latest log file" is 
>>>> stored, and upload that file. The output line telling its location will 
>>>> look like:
>>>>
>>>> Last Log File: 
>>>> [/home/anon/.config/gcloud/logs/2017.02.06/18.30.49.455744.log]
>>>>
>>>>
>>>> On Monday, February 6, 2017 at 12:58:05 PM UTC-5, Nick (Cloud Platform 
>>>> Support) wrote:
>>>>>
>>>>> Hey Adam,
>>>>>
>>>>> Could you capture the deployment logs using the flags "--verbosity 
>>>>> debug" and "--log-http", piping this output into the "ts" utility to 
>>>>> prepend a timestamp to each line, and then email me the logs? I'll be 
>>>>> able 
>>>>> to analyze what might be going on that way. On linux / Mac that will look 
>>>>> like:
>>>>>
>>>>> gcloud --quiet --verbosity debug --log-http app deploy app.yaml 
>>>>> --version ${VERSION} 2>&1 | ts | tee -a deploy_log.txt 
>>>>>
>>>>>
>>>>> (tee is used so that you can still read the output as it hits the 
>>>>> console, and note that you'll have to put whatever version you want in 
>>>>> the 
>>>>> command where ${VERSION} is written)
>>>>>
>>>>> On windows, you can use powershell to run the same command line after 
>>>>> creating the "ts" filter to prepend timestamps by running the following 
>>>>> line:
>>>>>
>>>>> filter timestamp {"$(Get-Date -Format s): $_"}
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Nick 
>>>>>
>>>>> On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
>>>>> Bittlingmayer wrote:
>>>>>>
>>>>>> Yes, it is the Flex Env.
>>>>>>
>>>>>> Reviewing the container build logs, it does not seem deterministic. 
>>>>>>  The total time varies, and the place in the process where multiple 
>>>>>> minutes 
>>>>>> pass between two log lines varies.
>>>>>>
>>>>>>
>>>>>> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform 
>>>>>> Support) wrote:
>>>>>>>
>>>>>>> Hey Adam,
>>>>&

[google-appengine] Re: Endpoints not working locally (for GO)

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Steven,

Thanks for letting us know. This seems like something that we could take a 
look at on the Public Issue Tracker. In order to produce a report there, 
we'll need a few more details though, for your specific case:

1. How do you run the devserver exactly?
2. What's the exact output?
3. How do you send the request to the server?
4. Can this be reproduced using the endpoints example from the github repo 
<https://github.com/GoogleCloudPlatform/golang-samples/tree/master/endpoints/getting-started>
?

With this information, we'll be able to begin work on reproducing the 
behaviour for specialists to take a look at and correct.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, February 18, 2017 at 7:38:48 AM UTC-5, Steven Kampen wrote:
>
> Looks like this is specific to OSX, judging by this report here: 
> http://stackoverflow.com/questions/42282294/404-when-migrating-go-appengine-app-from-ubuntu-to-macos
>
> I tested out a bunch of GCloud SDK versions until I found that the break 
> starts in v138.0.0, which uses Python Extensions v1.9.49. GCloud SDK 
> v137.0.1 uses Python Extensions v1.9.40, and works fine.
>
>
>
> On Saturday, 18 February 2017 12:22:38 UTC+1, Steven Kampen wrote:
>>
>> Thanks for the reply Nick,
>>
>> There is no stacktrace. The API service just seems not to be running. If 
>> I hit the endpoint path (verified from production) on the "main" port (8080 
>> by default, and which I assume is the intended behaviour) I get 404s. If I 
>> hit the endpoint path at the "API Server" host (port 55881 in the example 
>> above), then I get a response like "{app_id: dev~myprojectname, rtok: 
>> '0'}". I actually get this response from that host for all paths.
>>
>> I'm using version 1.9.48 of the SDK.
>>
>>
>>
>>
>> On Friday, 17 February 2017 01:46:45 UTC+1, Nick (Cloud Platform Support) 
>> wrote:
>>>
>>> Hey Steven,
>>>
>>> This kind of post - a specific-issue technical support question - would 
>>> be best sent to Stack Overflow, as there's a much larger user-base there 
>>> and their site is designed for that kind of post. This forum is meant for 
>>> more general discussion of the platform and services, design patterns, 
>>> free-form discussion not necessarily based on 1 question 1 answer. 
>>>
>>> But nonetheless, I'll be happy to assist here and possibly we can get 
>>> this question to a state where it can be posted to Stack Overflow.
>>>
>>> Some questions that jump out at me from reading your post:
>>>
>>> * What is the error that you see in development? Posting a full stack 
>>> trace helps to determine what went wrong
>>> * What version of the SDK are you using?
>>>
>>> I'll take a look at running the code from the tutorial you linked myself 
>>> and see if I can also see the error.
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Thursday, February 16, 2017 at 2:05:13 PM UTC-5, Steven Kampen wrote:
>>>>
>>>> I've previously used Python and Java SDKs (with endpoints), though it's 
>>>> been a while.
>>>>
>>>> When I setup a simple Go app with a single endpoint (similar to 
>>>> https://medium.com/google-cloud/go-cloud-endpoints-and-app-engine-64d1c78bea82#.8xz2ol18k)
>>>>  
>>>> I'm not able to get any response from the endpoints.
>>>>
>>>> I'm starting the app with both `goapp serve ./` and `dev_appserver.py 
>>>> ./` with the same result. *When deployed, the endpoints do work.*
>>>>
>>>> ```
>>>> INFO 2017-02-16 19:00:03,827 devappserver2.py:764] Skipping SDK 
>>>> update check.
>>>> INFO 2017-02-16 19:00:03,878 api_server.py:268] Starting API server 
>>>> at: http://localhost:55881
>>>> INFO 2017-02-16 19:00:03,881 dispatcher.py:199] Starting module 
>>>> "default" running at: http://localhost:8080
>>>> INFO 2017-02-16 19:00:03,887 admin_server.py:116] Starting admin 
>>>> server at: http://localhost:8000
>>>> ```
>>>>
>>>> I'm trying to access the local endpoint on port 8080.
>>>>
>>>

-- 
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/fea8c21d-a3f3-49f1-a62f-8c9fce2c0b92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoints not working locally (for GO)

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Steven,

This kind of post - a specific-issue technical support question - would be 
best sent to Stack Overflow, as there's a much larger user-base there and 
their site is designed for that kind of post. This forum is meant for more 
general discussion of the platform and services, design patterns, free-form 
discussion not necessarily based on 1 question 1 answer. 

But nonetheless, I'll be happy to assist here and possibly we can get this 
question to a state where it can be posted to Stack Overflow.

Some questions that jump out at me from reading your post:

* What is the error that you see in development? Posting a full stack trace 
helps to determine what went wrong
* What version of the SDK are you using?

I'll take a look at running the code from the tutorial you linked myself 
and see if I can also see the error.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 16, 2017 at 2:05:13 PM UTC-5, Steven Kampen wrote:
>
> I've previously used Python and Java SDKs (with endpoints), though it's 
> been a while.
>
> When I setup a simple Go app with a single endpoint (similar to 
> https://medium.com/google-cloud/go-cloud-endpoints-and-app-engine-64d1c78bea82#.8xz2ol18k)
>  
> I'm not able to get any response from the endpoints.
>
> I'm starting the app with both `goapp serve ./` and `dev_appserver.py ./` 
> with the same result. *When deployed, the endpoints do work.*
>
> ```
> INFO 2017-02-16 19:00:03,827 devappserver2.py:764] Skipping SDK update 
> check.
> INFO 2017-02-16 19:00:03,878 api_server.py:268] Starting API server 
> at: http://localhost:55881
> INFO 2017-02-16 19:00:03,881 dispatcher.py:199] Starting module 
> "default" running at: http://localhost:8080
> INFO 2017-02-16 19:00:03,887 admin_server.py:116] Starting admin 
> server at: http://localhost:8000
> ```
>
> I'm trying to access the local endpoint on port 8080.
>

-- 
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/09060a8f-afb8-4c1f-adbb-4bb0181406b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Use of Pandas in GAE

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Juan,

In the App Engine Standard Environment 
<https://cloud.google.com/appengine/docs/about-the-standard-environment>, 
the docs explain that code and libraries must be pure python 
<https://cloud.google.com/appengine/docs/python/runtime#Python_Pure_Python>:

All code for the Python runtime environment must be pure Python, and not 
include any C extensions or other code that must be compiled. 


However, for the Flexible Environment 
<https://cloud.google.com/appengine/docs/flexible/>, you can use C modules, 
certainly, along with any code that would run on a linux machine. The code 
runs inside a Docker container, but it's not quite the same as deploying on 
a Compute Engine instance and is more like programming for App Engine. 

You should check out the quickstart for a Flexible Environment python app 
<https://cloud.google.com/appengine/docs/flexible/python/quickstart> and 
then see about reading my last comment which showed a Dockerfile which 
would allow you to install libraries on the python instance container image.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, February 15, 2017 at 8:10:48 AM UTC-5, Juan Antonio Fernández 
Sánchez wrote:
>
> Hi Nick, 
>
> Thank you for your answer. The problem is that I would like to run these 
> libraries in a service inside a normal GAE app, not in a container in
> Compute Engine. 
>
> Thanks!
>
> El lunes, 13 de febrero de 2017, 20:12:12 (UTC+1), Nick (Cloud Platform 
> Support) escribió:
>>
>> Hey Juan,
>>
>> It could be because in installing the C -based python modules locally, 
>> pip is compiling C code for your system's architecture, which wouldn't 
>> translate to the deployed machine. If this is the case, see if the 
>> following works as a solution:
>>
>> You can write a Dockerfile for your Custom Runtime app that will install 
>> the requirements when the container image is built, that way it'll use the 
>> architecture of the container that will actually run the app. Here's an 
>> example Dockerfile from our python custom runtime github repository 
>> <https://github.com/GoogleCloudPlatform/python-runtime>:
>>
>> FROM gcr.io/google-appengine/python
>>
>> # Create a virtualenv for dependencies. This isolates these packages from
>> # system-level packages.
>> RUN virtualenv /env
>>
>> # Setting these environment variables are the same as running
>> # source /env/bin/activate.
>> ENV VIRTUAL_ENV /env
>> ENV PATH /env/bin:$PATH
>>
>> # Copy the application's requirements.txt and run pip to install all
>> # dependencies into the virtualenv.*ADD requirements.txt 
>> /app/requirements.txt
>> RUN pip install -r /app/requirements.txt*
>>
>> # Add the application source code.
>> ADD . /app
>>
>> # Run a WSGI server to serve the application. gunicorn must be declared as
>> # a dependency in requirements.txt.
>> CMD gunicorn -b :$PORT main:app
>>
>> You can see the lines which install dependencies in bold.
>>
>> Let me know how that works out for you! We could see about getting this 
>> caveat for custom runtime deployment and dependencies with c-based python 
>> modules documented if that turns out to be the case.
>>
>> In order for me to be able to test and reproduce what you've seen in 
>> future, could you also attach the requirements.txt to your reply?
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Sunday, February 12, 2017 at 3:13:01 PM UTC-5, Juan Antonio Fernández 
>> Sánchez wrote:
>>>
>>> Thank you so much for the answer Nick, I'm trying to do this without 
>>> success. 
>>>
>>> I've the dependencie in my requirements.txt file and in the module where 
>>> I import the module like this: import pandas as pd-
>>>
>>> If I try to execute the code I've this exception:
>>>
>>> ImportError: Missing required dependencies ['numpy']
>>>
>>> And if I add numpy in requirements.txt (executing it) and add the module 
>>> in the same file where I've pandas I've this exception:
>>>
>>> ImportError: 
>>> Importing the multiarray numpy extension module failed.  Most
>>> likely you are trying to import a failed build of numpy.
>>> If you're working with a numpy git repo, try `git clean -xdf` (removes 
>>> all
>>> files not under version control).  Otherwise reinstall numpy.
>>>
>>>
>>> I' m searching solutions in Stack Overflow but I don't find anything 
>>> interesting. I don't know if you have some simple example where I could see 
>

[google-appengine] Re: Datastore: how to design for huge time-series data

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Etienne,

You've correctly enumerated a few ways to transfer data from Cloud SQL to 
BigQuery: 

* export to CSV and load the CSV into BigQuery
* retrieve the data with an app and stream it into the BigQuery API
* export to Datastore and then import to BigQuery  

There are also other ways, such as using a mysqldump of your SQL DB 
. You should 
check the BigQuery "Loading Data" 
 documentation.

Let me know if you have any further questions, and I'll be happy to assist.

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, February 14, 2017 at 9:40:44 AM UTC-5, Etienne B. Roesch wrote:
>
> Hi,
>
> Sorry for the repeat, but I am trying to wrap my head around the 
> GAE-osphere and I am getting a bit confused;
>
> I need to store and retrieve/analyse timeseries data, of varying sizes and 
> resolutions; at the moment, the data is received and stored on GAE through 
> to Google Cloud SQL (python). That's not ideal. I foresee I will have to do 
> more analytics than data storage for the sake of storage, and I predict a 
> big throughput of data generally, and have thus been looking at 
> BigQuery/Datalab. I don't seem to find an obvious way to load data in 
> BigQuery from Cloud SQL, and would either have to export the data to Cloud 
> Storage in csv-ish, or directly stream the data from the GAE app to 
> BigQuery (which is currently my preferred option).
> Alternatively, there is the option of passing through to Google Datastore 
> first, which for me might be a more flexible way of preprocessing the data 
> before it enters in BigQuery.
>
> Is this the way to do things, or am I missing something?
>
> Thanks!
>
> Etienne
>
>
> On Tuesday, 13 August 2013 13:59:52 UTC+1, Martin Trummer wrote:
>>
>> I'm a newbie to the AppEngine datastore and like to know how to best 
>> design this use case:
>> there may be some time-series with huge amount of data: e.g. terra-bytes 
>> for one time-series
>> the transacations doc 
>>  
>> says about entity groups:
>>
>>- *"Every entity belongs to an entity group, a set of one or more 
>>entities that can be manipulated in a single transaction."*
>>- *"every entity with a given root entity as an ancestor is in the 
>>same entity group. All entities in a group are stored in the same 
>> Datastore 
>>node."*
>>
>> so does that mean, that all the terra-bytes of data for the huge 
>> time-series would end up *on one computer* somewhere in the AppEngine 
>> network?
>> if so: 
>>
>>- that's not a good idea, right?
>>- how to avoid it? should I split up the data in sections (e.g. per 
>>month) where each section has it's own kind/entity group?
>>
>>

-- 
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/71743636-3b96-44e7-a887-ed308d532b69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Working with unicode filenames on cloudstorage?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Attila,

This would be an excellent post to make on Stack Overflow, as this forum 
isn't quite meant for specific-issue technical support. We monitor our tags 
on Stack quite actively and there is also a much larger user-based there, 
so be sure to cross post at least this post, and in future consider simply 
posting to Stack - as of course, since we're there, there's no downside, 
only upsides of access to more users and keeping this forum on-topic. This 
forum is meant for general high level free-form discussion about the 
platform and services, architecture advice, etc. (basically things that 
don't fit on Stack Overflow).

Now, that said, I can help a bit. It seems that other users 
 
have found this exact issue with attempting to use the appengine gcs client 
library against the Development Server. From this I can ask two questions 
right away:

1. Have you tried running this code in production, and does it also fail? 
(any of the various versions attempted)

2. Have you tried using the other client library, which has been updated 
far more recently? You had linked it in your original post. Of course this 
would only be dodging the question of what's going on with the original 
(and official) library.

I'll be attempting to reproduce this issue while you get back to me on 
this. Feel free to add in any extra information or questions you have. 

Cheers,

Nick
Cloud Platform Community Support

On Monday, February 13, 2017 at 9:04:38 AM UTC-5, Attila-Mihaly Balazs 
wrote:
>
> Hello,
>
> I'm trying to create / delete files on google cloudstorage with unicode 
> characters in the name. GCS seems to support this alright, however the 
> client APIs seem to have problems.
>
> - Environment: Google Appengine Standard with Python 2.7. Tested locally 
> with dev_server 1.9.50. The library used (both locally and in production) 
> is the latest GoogleAppEngineCloudStorageClient [1] (1.9.22.1)
>
> - Some code snippets:
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(fn, 'w') as f_out: f_out.write('old')
>
> This gets me the traceback at [2]
>
> - Ok, how about manually encoding it?
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(fn.encode('utf-8'), 'w') as f_out: f_out.write('old')
>
> This just gets me several retries until the request is aborted [3]
>
> - There is the option of encoding it, however I don't believe this is 
> correct (this is just double quoting the filename):
>
> fn = u'/%s/á' % GS_BUCKET
> with gcs.open(urllib.quote(fn.encode('utf-8')), 'w') as f_out: 
> f_out.write('old')
>
> - I believe gcs.delete is also affected since I have the following 
> traceback in production [4]
>
> How are unicode filenames supposed to be used with the cloudstorage 
> library? Also, is the cloudstorage library supposed to be used at all? 
> Looking around I found the google-cloud-storage library on PyPi (
> https://pypi.python.org/pypi/google-cloud-storage) which also seems to be 
> an official Google project and perhaps has better support for unicode?
>
> Attila 
>
> [1] https://pypi.python.org/pypi/GoogleAppEngineCloudStorageClient
> [2] Traceback with u'...'
> /usr/local/google_appengine_1.9.50/google/appengine/dist27/urllib.py:1277: 
> UnicodeWarning: Unicode equal comparison failed to convert both arguments 
> to Unicode - interpreting them as being unequal
>   return ''.join(map(quoter, s))
> ERROR2017-02-13 13:52:30,401 webapp2.py:1552] u'\xe1'
> Traceback (most recent call last):
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1535, in __call__
> rv = self.handle_exception(request, response, e)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1529, in __call__
> rv = self.router.dispatch(request, response)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1278, in default_dispatcher
> return route.handler_adapter(request, response)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 1102, in __call__
> return handler.dispatch()
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 572, in dispatch
> return self.handle_exception(e, self.app.debug)
>   File "/usr/local/google_appengine_1.9.50/lib/webapp2-2.5.2/webapp2.py", 
> line 570, in dispatch
> return method(*args, **kwargs)
>   File "/tmp/gcs_test_unicode_names/main.py", line 14, in get
> with gcs.open(fn, 'w') as f_out: f_out.write('old')
>   File "/tmp/gcs_test_unicode_names/lib/cloudstorage/cloudstorage_api.py", 
> line 91, in open
> filename = api_utils._quote_filename(filename)
>   File "/tmp/gcs_test_unicode_names/lib/cloudstorage/api_utils.py", line 
> 94, in _quote_filename
> return urllib.quote(filename)
>   File 
> "/usr/local/google_appengine_1.9.50/google/appengine/dist27/urllib.py", 
> line 1277, in quote
> return 

[google-appengine] Re: deploy is very slow

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Luis, 

The best way in fact would be to create a Public Issue Tracker 
<https://code.google.com/p/google-cloud-platform/issues/list>thread, and 
we'll be able to follow up there. Post the link here once you've created a 
thread, and I'll be happy to assist, sending you an email which you can 
reply to, attaching the log. 

Cheers,

Nick
Cloud Platform Community Support

On Sunday, February 12, 2017 at 11:57:14 AM UTC-5, Luis F De Pombo wrote:
>
> Hi Nick,
> I am having the same issue as Adam but I am using a nodejs Flex env. I 
> have the file you point to, what is the best email to get this to you? 
> Thank you.
>
> On Monday, February 6, 2017 at 10:40:48 AM UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Just a quick update:
>>
>> As well, to avoid the timestamp filtering commands above, you could 
>> simply run the deployment with the --verbosity debug and --log-http flags 
>> and then run gcloud info to check for where the "latest log file" is 
>> stored, and upload that file. The output line telling its location will 
>> look like:
>>
>> Last Log File: 
>> [/home/anon/.config/gcloud/logs/2017.02.06/18.30.49.455744.log]
>>
>>
>> On Monday, February 6, 2017 at 12:58:05 PM UTC-5, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Adam,
>>>
>>> Could you capture the deployment logs using the flags "--verbosity 
>>> debug" and "--log-http", piping this output into the "ts" utility to 
>>> prepend a timestamp to each line, and then email me the logs? I'll be able 
>>> to analyze what might be going on that way. On linux / Mac that will look 
>>> like:
>>>
>>> gcloud --quiet --verbosity debug --log-http app deploy app.yaml 
>>> --version ${VERSION} 2>&1 | ts | tee -a deploy_log.txt 
>>>
>>>
>>> (tee is used so that you can still read the output as it hits the 
>>> console, and note that you'll have to put whatever version you want in the 
>>> command where ${VERSION} is written)
>>>
>>> On windows, you can use powershell to run the same command line after 
>>> creating the "ts" filter to prepend timestamps by running the following 
>>> line:
>>>
>>> filter timestamp {"$(Get-Date -Format s): $_"}
>>>
>>>
>>> Cheers,
>>>
>>> Nick 
>>>
>>> On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
>>> Bittlingmayer wrote:
>>>>
>>>> Yes, it is the Flex Env.
>>>>
>>>> Reviewing the container build logs, it does not seem deterministic. 
>>>>  The total time varies, and the place in the process where multiple 
>>>> minutes 
>>>> pass between two log lines varies.
>>>>
>>>>
>>>> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform 
>>>> Support) wrote:
>>>>>
>>>>> Hey Adam,
>>>>>
>>>>> Are you deploying a Flexible Environment app? If so, what do the 
>>>>> container builder logs from the Console show as far as activity during 
>>>>> this 
>>>>> time?
>>>>>
>>>>> Also, is this still occurring, or was it only for a certain period of 
>>>>> time? If it's transient, it might just be a momentary service 
>>>>> degradation, 
>>>>> which for a Beta product is to be expected at this stage. When a product 
>>>>> goes into General Availability, we'll often have certain Service Level 
>>>>> targets in terms of latency, uptime, that you can rely on (for example, 
>>>>> read 
>>>>> here <https://cloud.google.com/compute/sla> for Compute Engine SLA's)
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Nick
>>>>> Cloud Platform Community Support
>>>>>
>>>>> On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
>>>>> Bittlingmayer wrote:
>>>>>>
>>>>>> Deployment with gcloud deploy app is slow (in the low dozens of 
>>>>>> minutes).
>>>>>>
>>>>>> The build is fast, it is the push steps that are slow.
>>>>>>
>>>>>> Both steps like Mounted from google_appengine/python and Updating 
>>>>>> service [test]...\ ie steps that are in the datacentre, not the 
>>>>>> upload itself.
>>>>>>
>>>>>> Thus the size of the code seems to have no effect, it is small enough 
>>>>>> in this case.  It happens with both python 2 and 3.
>>>>>>
>>>>>> Is there a way to increase an allocation to speed this up?  Are there 
>>>>>> other factors?
>>>>>>
>>>>>

-- 
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/8084d4d6-2599-4377-8c3a-3fce6525%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoint API not working properly via API Explorer after deployment to App Engine Standard

['Nick (Cloud Platform Support)' via Google App Engine]

Hey George,

That's great to hear. Keep in mind that we also monitor our tags on Stack 
Overflow, so I'll be there as well if you ask a question, haha. Glad to 
have been of assistance.

One last question I have, though, is what you meant about manual scaling. 
Could you share some more information about that? How was manual scaling 
involved in this issue's appearance / solution?

Cheers,

Nick
Cloud Platform Community Support

On Saturday, February 11, 2017 at 4:14:37 AM UTC-5, George Sxi wrote:
>
> Many thanks for your insight Nick, in my case, apart from the issue you 
> described I have also forgotten to include "manual scaling" in the relevant 
> .xml which was causing the issue.
>  
> Let me point out that your reply was the fastest and most accurate from 
> any of my stack overflow posts :) 
> Will keep in mind to try there first though. 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/c9c53327-5405-4140-807d-ec255e8be660%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Use of Pandas in GAE

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Juan,

It could be because in installing the C -based python modules locally, pip 
is compiling C code for your system's architecture, which wouldn't 
translate to the deployed machine. If this is the case, see if the 
following works as a solution:

You can write a Dockerfile for your Custom Runtime app that will install 
the requirements when the container image is built, that way it'll use the 
architecture of the container that will actually run the app. Here's an 
example Dockerfile from our python custom runtime github repository 
<https://github.com/GoogleCloudPlatform/python-runtime>:

FROM gcr.io/google-appengine/python

# Create a virtualenv for dependencies. This isolates these packages from
# system-level packages.
RUN virtualenv /env

# Setting these environment variables are the same as running
# source /env/bin/activate.
ENV VIRTUAL_ENV /env
ENV PATH /env/bin:$PATH

# Copy the application's requirements.txt and run pip to install all
# dependencies into the virtualenv.*ADD requirements.txt /app/requirements.txt
RUN pip install -r /app/requirements.txt*

# Add the application source code.
ADD . /app

# Run a WSGI server to serve the application. gunicorn must be declared as
# a dependency in requirements.txt.
CMD gunicorn -b :$PORT main:app

You can see the lines which install dependencies in bold.

Let me know how that works out for you! We could see about getting this 
caveat for custom runtime deployment and dependencies with c-based python 
modules documented if that turns out to be the case.

In order for me to be able to test and reproduce what you've seen in 
future, could you also attach the requirements.txt to your reply?

Cheers,

Nick
Cloud Platform Community Support

On Sunday, February 12, 2017 at 3:13:01 PM UTC-5, Juan Antonio Fernández 
Sánchez wrote:
>
> Thank you so much for the answer Nick, I'm trying to do this without 
> success. 
>
> I've the dependencie in my requirements.txt file and in the module where I 
> import the module like this: import pandas as pd-
>
> If I try to execute the code I've this exception:
>
> ImportError: Missing required dependencies ['numpy']
>
> And if I add numpy in requirements.txt (executing it) and add the module 
> in the same file where I've pandas I've this exception:
>
> ImportError: 
> Importing the multiarray numpy extension module failed.  Most
> likely you are trying to import a failed build of numpy.
> If you're working with a numpy git repo, try `git clean -xdf` (removes all
> files not under version control).  Otherwise reinstall numpy.
>
>
> I' m searching solutions in Stack Overflow but I don't find anything 
> interesting. I don't know if you have some simple example where I could see 
> it working.
> I would like use only pandas but i don't know if in the future I will need 
> numpy.
>
> Could you help me?
>
> Thank you so mucho, any help will be welcome.
>
>
>
>
> El jueves, 9 de febrero de 2017, 20:07:42 (UTC+1), Nick (Cloud Platform 
> Support) escribió:
>>
>> Hey Juan Antonio, 
>>
>> As you noted correctly, in the Standard Environment 
>> <https://cloud.google.com/appengine/docs/about-the-standard-environment>, 
>> only pure python apps are supported. However in the Flexible Environment 
>> <https://cloud.google.com/appengine/docs/flexible/>, there is no such 
>> restriction, and you can run any python app, regardless of it's use of C 
>> libraries! All you'll need to do is go into your python app's app.yaml 
>> file and add the line "env: flex". Now, if you've installed the pandas 
>> library to a lib/ folder in your app's directory and added the folder to 
>> the python import path (sys.path), you'll be able to import pandas without 
>> an issue.
>>
>> And of course, you can use Compute Engine as well, depending on what 
>> exactly you'd prefer. What purpose are you deploying machines running 
>> pandas for? Maybe I could help if you've got questions about the trade-offs 
>> between a Flexible Environment and Compute Engine deployment.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, February 9, 2017 at 12:50:44 PM UTC-5, Juan Antonio 
>> Fernández Sánchez wrote:
>>>
>>> Hi everyone!
>>>
>>> I'm trying to run Pandas library in GAE app. I know that it use C 
>>> internally and I'm wondering if exist any simple solution to execute this 
>>> is GAE of if I've to think to deploy this microservice in a Compute Engine 
>>> container.
>>>
>>> Any help will be welcome, thank you so much!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine"

[google-appengine] Re: Sudden Ancestor Queries Issue

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Rajesh,

With the low amount of information given here, I can't really say what 
could be causing this. Do you think you could share the text of the error?

The Cloud Status Dashboard  is showing no 
issue, and I can't find any mention of any issue internally. In the absence 
of these and the absence of other users reporting the same, I'd say this is 
likely to be an issue with the entities themselves, since as you say the 
code hasn't changed. But this could also be a transient and rare issue 
affecting just your app for a given time-frame - we can't know any of this 
without more details.

Cheers,

Nick
Cloud Platform Community Support

On Friday, February 10, 2017 at 9:56:48 AM UTC-5, Rajesh Gupta wrote:
>
> Hi,
> Suddenly since 12 hrs, our software is throwing intermittent errors when 
> ancestor queries are done for some data and namespaces. 
> We are also finding out for more details and will share as we find.
>
> There are no changes in that part of the code, which is executing fine for 
> long  time.
>
> Anyone having similar issues please share. 
>
> Regards,
> Rajesh
> *www.VeersoftSolutions.com *
> *www.GainERP.com *
> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
> Mobile*
>
>

-- 
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/783b083e-a818-4115-96c3-4aa0af6ccd8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: gcloud sdk on Mac Sierra

['Nick (Cloud Platform Support)' via Google App Engine]

Hey gdenn,

Sourcing .bash_profile is the right thing to do, as it's there that the 
path is augmented to add gcloud and its completions. You should check if 
another file, like ~/.bashrc is being sourced, and if necessary, add 
"source ~/.bash_profile" in there, to ensure it is sourced every time and 
doesn't need to be run as a command by hand in future.

I found a link online to a github issue where a user saw similar issues 
 (I found it by googling the 
error message, a common and very useful means to debug issues!) on Mac OS 
X. Check the thread for advice on possible solutions, such as installing 
bash_completion. Be aware that this isn't a link to Google documentation so 
you assume responsibility for it, and I'm far from guaranteeing it as a 
solution. But it's one possible avenue to look into.

Another issue the link raises is whether or not you're even running a bash 
shell. Zsh has a different syntax and you may need to figure out how to 
augment your path and set up completion. There's a gist on github 
 purporting to show this, but 
note that this is also not one of our links and I can't vouch for it - 
you'll have to study it yourself for security, applicability, etc.

Let me know if you have any further questions, and how all this works out 
for you; I'll be happy to help!

Nick
Cloud Platform Community Support
 

On Friday, February 10, 2017 at 10:02:10 AM UTC-5, gdenn wrote:
>
> Hi,
>
> i recently changed to macOs and i am currently running their newest 
> Version "macOS Sierra Version 10.12".
> Problems started after i installed gcloud cli tools from the official page 
> https://cloud.google.com/sdk/docs/quickstart-mac-os-x . 
> I tried both (Darwin_x_86 and Darwin_x_86_64) but after installation there 
> is no env variable set for gcloud. So i look into the ~/.bash_profile and 
> what i see is 
> https://gist.github.com/Rapdrei/4a97512039cdc2c835e42e6e4dc453d3
>
> After that i call .bash_profile manually by source ~/.bash_profile and 
> receive the error 
> https://gist.github.com/Rapdrei/7fb2277309941d3621a9ac99b19b092b .
>
> Could someone reproduce the problem or even solve it?
> best,
> gdenn
>

-- 
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/6703d274-65fa-44db-b3a5-e5b502e9f9c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Payment card marked "The account is closed", cant settle bills

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Arnold!

You should open a billing issue 
 for this 
question, as this forum is intended for discussion of development on the 
platform and services, design patterns, architecture, etc.

Wishing you the best of luck with the billing issue,

Nick
Cloud Platform Community Support

On Thursday, February 9, 2017 at 9:54:12 AM UTC-5, Arnold Minde wrote:
>
>
> It seem I cannot pay for my last month bill because the Payment card in 
> billing section is marked "The account is closed". I suspect google tried 
> to bill the card and it failed for whatever reason, and decided to mark it 
> as such.
>
> I use the same card in other billing accounts, and in those other accounts 
> automatic payment for last month were successful. I have used the same card 
> to settle my gogle cloud platform bills for more than a year.
>
> Could someone point me out to what I can do to remove this status and use 
> the same card to settle my bills?
>
> Best Regards,
> Arnold.
>

-- 
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/106ba1b2-f31d-4569-b379-2a18baee2274%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Use of Pandas in GAE

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Juan Antonio, 

As you noted correctly, in the Standard Environment 
, 
only pure python apps are supported. However in the Flexible Environment 
, there is no such 
restriction, and you can run any python app, regardless of it's use of C 
libraries! All you'll need to do is go into your python app's app.yaml file 
and add the line "env: flex". Now, if you've installed the pandas library 
to a lib/ folder in your app's directory and added the folder to the python 
import path (sys.path), you'll be able to import pandas without an issue.

And of course, you can use Compute Engine as well, depending on what 
exactly you'd prefer. What purpose are you deploying machines running 
pandas for? Maybe I could help if you've got questions about the trade-offs 
between a Flexible Environment and Compute Engine deployment.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 9, 2017 at 12:50:44 PM UTC-5, Juan Antonio Fernández 
Sánchez wrote:
>
> Hi everyone!
>
> I'm trying to run Pandas library in GAE app. I know that it use C 
> internally and I'm wondering if exist any simple solution to execute this 
> is GAE of if I've to think to deploy this microservice in a Compute Engine 
> container.
>
> Any help will be welcome, thank you so much!
>

-- 
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/d4125a1c-2650-4a98-8a74-6b40f5557256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoint API not working properly via API Explorer after deployment to App Engine Standard

['Nick (Cloud Platform Support)' via Google App Engine]

 {
> 
> Log.info("YEAHH");
>
> // As an admin, the app has access to read and write all 
> data, regardless of Security Rules.
> DatabaseReference ref = 
> FirebaseDatabase.getInstance().getReference(stringFBREF_MY_FIREBASE_TABLE);
>
> if(ref != null){
> Log.info("REFERENCE FOR DB: " + ref.toString());
>         ref.push().setValue("I_can_write_to_firebase!");
> }else{
> Log.info("Database reference is null :( ");
> }
> } catch (Exception error) {
> Log.info("ERROR: " + error.getMessage());
> Log.info("ERROR: You have already initialized 
> FirebaseApp...");
> }
>
> } catch (FileNotFoundException e) {
> e.printStackTrace();
> }
>
>
>
> }
>
> }
>
>
>  
>
> On Thursday, February 9, 2017 at 2:29:47 AM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey George,
>>
>> First off, I'll say I'm glad you've taken the time to provide such 
>> detailed explanation of what steps you've followed. You'd be surprised how 
>> often this level of detail (the minimum really needed to properly analyze 
>> an issue) is not given, so thank you very much for that! This should be an 
>> example post for other users!
>>
>> Second, usually specific-issue technical support questions like this 
>> should be handled at Stack Overflow on one of our related tags. We monitor 
>> there just as consistently as this forum, while this one is both A) less 
>> supplied with other helpful users and B) not intended for this 1-on-1 
>> format of support. So, you might consider posting questions like this there 
>> in the future, or even posting there now, but after we gather some more 
>> information necessary to look deeper.
>>
>> My initial thought about what might be going wrong is that it's difficult 
>> to determine without seeing any code. You should gather the code in the 
>> endpoints method so we can see why it is that it might return 200 yet fail 
>> to write an entity.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support 
>>
>> On Wednesday, February 8, 2017 at 10:45:52 AM UTC-5, George Sxi wrote:
>>>
>>> Hello everyone!
>>>
>>> I would like to pose the following question..
>>>
>>> I have successfully created a sample backend using cloud endpoints 
>>> frameworks which simply performs a REST call using POST and writes a value 
>>> in a Firebase folder.
>>> In order to do this:
>>> 1)  i used the "Hello Endpoints" sample which is created when you add 
>>> the module in android studio as a starting point. 
>>> 2)  After importing the relevant libraries, annotating the API and 
>>> adding the extra functionality I run the backend in my localhost 
>>> 3)  To test the process I used the  API explorer *locally* and passed a 
>>> value in the "name" field using "Execute without OAuth" 
>>> 4) Regardless of the value passed the process should write the same 
>>> value in Firebase.
>>>
>>> Up to this point everything worked like a charm.
>>>
>>> The next step was to try and deploy the backend on Google App Engine and 
>>> try it from there.
>>> Using the "*Deploy Module to app engine*" option from Android studio 
>>> the backend was successfully deployed on App Engine Standard and started 
>>> serving requests.
>>>
>>> Now doing the exact same thing when I try to use the cloud platform API 
>>> explorer (with the myapp.appspot.com link )to test the API I get the 
>>> 200OK http answer to my POST but the Firebase entry is not written.
>>>
>>> Can anyone provide some insight into this?? 
>>>
>>> Since it is working properly in the localhost deployment but not when 
>>> deployed on App Engine I suspect something is happening access-wise but I 
>>> cannot find it..
>>>
>>> Please note that I have also tried it with public read/write Firebase 
>>> rules and by using the "*authorize and execute"* option in API explorer.
>>>
>>> Happy to provide any additional info if required.
>>>
>>> Thanks!
>>>
>>
> On Thursday, February 9, 2017 at 2:29:47 AM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
&g

[google-appengine] Re: google Calendar

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Thamotharakannan,

Unfortunately, this forum is not intended for this style of post, asking 
for 1-on-1 technical support on a specific issue. This forum is meant more 
for high level and general discussion of the platform and services of App 
Engine. 

You should post your code to Stack Overflow  
(where there are many more users who are happy to answer a question in this 
format) along with an explanation of how you are running the code (what 
kind of environment is it deployed to?) and very important to include, what 
the actual error message you saw was.

When you post to Stack Overflow , feel free to 
post here with a link to the question and I'll be happy to take a look. 

Cheers,

Nick
Cloud Platform Community Support
  

On Wednesday, February 8, 2017 at 9:03:18 AM UTC-5, Thamotharakannan 
Ganeshan wrote:
>
> Hi 
> google Calendar event can't insert
> my code
> function create_calendar_event($token , $description, $leaveDate , 
> $toLeaveDate ){
> try{
> $title = 'Leave today';
> $start_time = '00:00'; $end_time = '23:59';
> $timezone = 'Asia/Kolkata';
> $start = array(
> "dateTime" => $leaveDate . "T" . $start_time . ":00",
> "timeZone" => $timezone
> );
> $end = array(
> "dateTime" => $toLeaveDate . "T" . $end_time . ":00",
> "timeZone" => $timezone
> );
> $headerarray = array(
> 'Content-type: application/json',
> 'Authorization: Bearer ' . $token->access_token,
> 'X-JavaScript-User-Agent: Google APIs Explorer'
> );
> $post_data = array(
> "start"   => $start,
> "end" => $end,
> "summary" => $title,
> "description" => $description
> );
>  
> $post_data = json_encode($post_data);
> $calendar_id = 'primary';
> $url = 'https://www.googleapis.com/calendar/v3/calendars/' . $calendar_id 
> . '/events';
> $result = $this->curlRequest($url, $headerarray, $post_data);
> return $result;
> }catch(Exception $e){
> // Exception
> }
> }
>  function curlRequest($url,$headerarray,$post_data, $curl_call = true){
> try{
> $ch = curl_init();
> curl_setopt($ch, CURLOPT_URL, $url);
> curl_setopt($ch, CURLOPT_POST, 1);
> curl_setopt($ch, CURLOPT_HTTPGET, true);
> curl_setopt($ch, CURLOPT_HTTPHEADER, $headerarray);
> curl_setopt($ch, CURLOPT_POSTFIELDS, $post_data);
> curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); 
> $server_output = curl_exec($ch);
> $info = curl_getinfo($ch);
> $header_size = curl_getinfo($ch, CURLINFO_HEADER_SIZE);
> $headers = substr($server_output, 0, $header_size);
> $response = substr($server_output, $header_size);
> $data = array();
> if($info['http_code'] == 200) {
> $data['headers'] = $headers;
> $data['response'] = json_decode($response);
> $data['status'] = 'SUCCESS';
> } else {
> if($info['http_code'] == 404) {
> $data['response'] = 'Not Found';
> $data['status'] = 'ERROR';
> } else {
> $data['response'] = json_decode($response);
> $data['status'] = 'ERROR';
> }
> $data['headers'] = $headers;
> }
> curl_close($ch);
> return $data;
> } catch (Exception $e) {
> // Exception
> }
> }
>

-- 
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/d1ccefe3-b250-4410-bf7e-0fd2371c217f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Endpoint API not working properly via API Explorer after deployment to App Engine Standard

['Nick (Cloud Platform Support)' via Google App Engine]

Hey George,

First off, I'll say I'm glad you've taken the time to provide such detailed 
explanation of what steps you've followed. You'd be surprised how often 
this level of detail (the minimum really needed to properly analyze an 
issue) is not given, so thank you very much for that! This should be an 
example post for other users!

Second, usually specific-issue technical support questions like this should 
be handled at Stack Overflow on one of our related tags. We monitor there 
just as consistently as this forum, while this one is both A) less supplied 
with other helpful users and B) not intended for this 1-on-1 format of 
support. So, you might consider posting questions like this there in the 
future, or even posting there now, but after we gather some more 
information necessary to look deeper.

My initial thought about what might be going wrong is that it's difficult 
to determine without seeing any code. You should gather the code in the 
endpoints method so we can see why it is that it might return 200 yet fail 
to write an entity.

Cheers,

Nick
Cloud Platform Community Support 

On Wednesday, February 8, 2017 at 10:45:52 AM UTC-5, George Sxi wrote:
>
> Hello everyone!
>
> I would like to pose the following question..
>
> I have successfully created a sample backend using cloud endpoints 
> frameworks which simply performs a REST call using POST and writes a value 
> in a Firebase folder.
> In order to do this:
> 1)  i used the "Hello Endpoints" sample which is created when you add the 
> module in android studio as a starting point. 
> 2)  After importing the relevant libraries, annotating the API and adding 
> the extra functionality I run the backend in my localhost 
> 3)  To test the process I used the  API explorer *locally* and passed a 
> value in the "name" field using "Execute without OAuth" 
> 4) Regardless of the value passed the process should write the same value 
> in Firebase.
>
> Up to this point everything worked like a charm.
>
> The next step was to try and deploy the backend on Google App Engine and 
> try it from there.
> Using the "*Deploy Module to app engine*" option from Android studio the 
> backend was successfully deployed on App Engine Standard and started 
> serving requests.
>
> Now doing the exact same thing when I try to use the cloud platform API 
> explorer (with the myapp.appspot.com link )to test the API I get the 
> 200OK http answer to my POST but the Firebase entry is not written.
>
> Can anyone provide some insight into this?? 
>
> Since it is working properly in the localhost deployment but not when 
> deployed on App Engine I suspect something is happening access-wise but I 
> cannot find it..
>
> Please note that I have also tried it with public read/write Firebase 
> rules and by using the "*authorize and execute"* option in API explorer.
>
> Happy to provide any additional info if required.
>
> 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/71588361-e137-44af-baf1-fcd83b69740a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: 4 Instance spinning in 4 secs

['Nick (Cloud Platform Support)' via Google App Engine]

... and as a last bit of additional information, if you use gcloud beta 
logging read, be sure you read the help document for that command (gcloud 
beta logging read --help) and pay special attention to the need to use 
filters <https://cloud.google.com/logging/docs/view/advanced_filters> to 
specify the resource you want to target.

On Tuesday, February 7, 2017 at 11:33:23 AM UTC-5, Nick (Cloud Platform 
Support) wrote:
>
> One thing I'd add to the above excellent comment by Nicholas G:
>
> There's currently a beta feature in the gcloud tool which can read app 
> logs and show any info, warning, error, etc. logs from within the requests, 
> while the gcloud app logs read won't show this information:
>
> gcloud beta logging read
>
>
> As to your last comment, Rajesh, yes I'd say that gathering logs like this 
> will contain information you probably don't want to share with the public, 
> so you would want to either email it to us directly or open a Public 
> Issue Tracker <http://code.google.com/p/googleappengine/issues/list> 
> report with the label "Restrict-View-EditIssue". 
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, February 7, 2017 at 10:05:19 AM UTC-5, Nicholas (Google Cloud 
> Support) wrote:
>>
>> To get logs for a specific GAE service, you can use one of the following:
>>
>>- Selecting the text of the logs in the browser when viewing the 
>>Logging window in the Developers Console.  With most modern browsers, 
>> it's 
>>possible for web site designers to control how content is copied and 
>> pasted 
>>despite how it may be rendered on the page.  Thus, some page components 
>>that seem as though they won't look right when pasted elsewhere in plain 
>>text can actually look readable.
>>- Cloud SDK in the terminal with app logs read 
>><https://cloud.google.com/sdk/gcloud/reference/app/logs/read>.  The 
>>output of such commands is generally formatted to be read in monospace, 
>>plain text window and are therefore suitable for plain text exchanges.
>>
>> * gcloud app logs read --level=debug --service= 
>> --version=*
>>
>>- Create an Export into a sink like Cloud Storage 
>>
>> <https://cloud.google.com/logging/docs/export/configure_export_v2#errors_exporting_to_cloud_storage>
>>  
>>so that you could then share the logs as files in an email
>>
>> These are generally very useful ways to troubleshoot as it makes it 
>> easier search key terms from logs in forums such as Google, Stack Overflow 
>> or this Google Group.  I hope the above is helpful.
>>
>> On Tuesday, February 7, 2017 at 12:08:05 AM UTC-5, Rajesh Gupta wrote:
>>>
>>> Hello Nick,
>>>
>>> Is there a way to get the txt of the log files.  I don't see any options 
>>> to export the logs for the given time to a txt file.
>>>
>>> I cannot pass on the text logs to the group, as url's contain some 
>>> information.  I will open a production case.  
>>>  
>>> Regards,
>>> Rajesh
>>> *www.VeersoftSolutions.com <http://www.veersoftsolutions.com/>*
>>> *www.GainERP.com <https://www.gainerp.com/>*
>>> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
>>> Mobile*
>>>
>>>
>>>
>>>
>>> On Thu, Dec 29, 2016 at 5:12 AM, 'Nick (Cloud Platform Support)' via 
>>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>>
>>>> Hey Rajesh,
>>>>
>>>> The scaling behaviour on your app is highly dependent on the contents 
>>>> of your app.yaml / appengine-web.xml file. Could you post that? 
>>>>
>>>> Also, it would be good to get a larger time-window selection of logs in 
>>>> text format (rather than screenshot) along with a screenshot of the 
>>>> instance numbers graph covering the same time period. This would be very 
>>>> helpful in reasoning about what is happening here.
>>>>
>>>> If you have any further questions, feel free to send them along with 
>>>> your reply and I'll be glad to assist in answering them. 
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Support  
>>>>
>>>>
>>>> On Sunday, December 25, 2016 at 9:56:07 PM UTC-5, Rajesh Gupta wrote:
>>>>
>>>>> Sorry, in 4 minutes (not 4 sec) there are 4 new instances.  You can 
>>>>> see t

Re: [google-appengine] Re: 4 Instance spinning in 4 secs

['Nick (Cloud Platform Support)' via Google App Engine]

One thing I'd add to the above excellent comment by Nicholas G:

There's currently a beta feature in the gcloud tool which can read app logs 
and show any info, warning, error, etc. logs from within the requests, 
while the gcloud app logs read won't show this information:

gcloud beta logging read


As to your last comment, Rajesh, yes I'd say that gathering logs like this 
will contain information you probably don't want to share with the public, 
so you would want to either email it to us directly or open a Public Issue 
Tracker <http://code.google.com/p/googleappengine/issues/list> report with 
the label "Restrict-View-EditIssue". 

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, February 7, 2017 at 10:05:19 AM UTC-5, Nicholas (Google Cloud 
Support) wrote:
>
> To get logs for a specific GAE service, you can use one of the following:
>
>- Selecting the text of the logs in the browser when viewing the 
>Logging window in the Developers Console.  With most modern browsers, it's 
>possible for web site designers to control how content is copied and 
> pasted 
>despite how it may be rendered on the page.  Thus, some page components 
>that seem as though they won't look right when pasted elsewhere in plain 
>text can actually look readable.
>- Cloud SDK in the terminal with app logs read 
><https://cloud.google.com/sdk/gcloud/reference/app/logs/read>.  The 
>output of such commands is generally formatted to be read in monospace, 
>plain text window and are therefore suitable for plain text exchanges.
>
> * gcloud app logs read --level=debug --service= 
> --version=*
>
>- Create an Export into a sink like Cloud Storage 
>
> <https://cloud.google.com/logging/docs/export/configure_export_v2#errors_exporting_to_cloud_storage>
>  
>so that you could then share the logs as files in an email
>
> These are generally very useful ways to troubleshoot as it makes it easier 
> search key terms from logs in forums such as Google, Stack Overflow or this 
> Google Group.  I hope the above is helpful.
>
> On Tuesday, February 7, 2017 at 12:08:05 AM UTC-5, Rajesh Gupta wrote:
>>
>> Hello Nick,
>>
>> Is there a way to get the txt of the log files.  I don't see any options 
>> to export the logs for the given time to a txt file.
>>
>> I cannot pass on the text logs to the group, as url's contain some 
>> information.  I will open a production case.  
>>  
>> Regards,
>> Rajesh
>> *www.VeersoftSolutions.com <http://www.veersoftsolutions.com/>*
>> *www.GainERP.com <https://www.gainerp.com/>*
>> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
>> Mobile*
>>
>>
>>
>>
>> On Thu, Dec 29, 2016 at 5:12 AM, 'Nick (Cloud Platform Support)' via 
>> Google App Engine <google-appengine@googlegroups.com> wrote:
>>
>>> Hey Rajesh,
>>>
>>> The scaling behaviour on your app is highly dependent on the contents of 
>>> your app.yaml / appengine-web.xml file. Could you post that? 
>>>
>>> Also, it would be good to get a larger time-window selection of logs in 
>>> text format (rather than screenshot) along with a screenshot of the 
>>> instance numbers graph covering the same time period. This would be very 
>>> helpful in reasoning about what is happening here.
>>>
>>> If you have any further questions, feel free to send them along with 
>>> your reply and I'll be glad to assist in answering them. 
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support  
>>>
>>>
>>> On Sunday, December 25, 2016 at 9:56:07 PM UTC-5, Rajesh Gupta wrote:
>>>
>>>> Sorry, in 4 minutes (not 4 sec) there are 4 new instances.  You can see 
>>>> that betwee 23:32 & 23:36.
>>>>
>>>> There are only 6-7 requests during that time.
>>>>
>>>> On Mon, Dec 26, 2016 at 7:57 AM, Rajesh Gupta <
>>>> rajesh.gu...@veersoftsolutions.com> wrote:
>>>>
>>>>> Hello 
>>>>> Following is the traffic to our website.  
>>>>>
>>>>> You can see suddenly, there are new four instances ('i' in the orange 
>>>>> color denotes log.warning).  I do log.warning in my context listener.  
>>>>> Between 23:32 & 23:36, ie 4 secs, there are new four instances.  The 
>>>>> traffic could have well served with the normal instance.  Each of the 
>>>>> instance spinning and serving is taking approx 22 sec.  
>&g

[google-appengine] Re: deploy is very slow

['Nick (Cloud Platform Support)' via Google App Engine]

Just a quick update:

As well, to avoid the timestamp filtering commands above, you could simply 
run the deployment with the --verbosity debug and --log-http flags and then 
run gcloud info to check for where the "latest log file" is stored, and 
upload that file. The output line telling its location will look like:

Last Log File: [/home/anon/.config/gcloud/logs/2017.02.06/18.30.49.455744.log]


On Monday, February 6, 2017 at 12:58:05 PM UTC-5, Nick (Cloud Platform 
Support) wrote:
>
> Hey Adam,
>
> Could you capture the deployment logs using the flags "--verbosity debug" 
> and "--log-http", piping this output into the "ts" utility to prepend a 
> timestamp to each line, and then email me the logs? I'll be able to analyze 
> what might be going on that way. On linux / Mac that will look like:
>
> gcloud --quiet --verbosity debug --log-http app deploy app.yaml --version 
> ${VERSION} 2>&1 | ts | tee -a deploy_log.txt 
>
>
> (tee is used so that you can still read the output as it hits the console, 
> and note that you'll have to put whatever version you want in the command 
> where ${VERSION} is written)
>
> On windows, you can use powershell to run the same command line after 
> creating the "ts" filter to prepend timestamps by running the following 
> line:
>
> filter timestamp {"$(Get-Date -Format s): $_"}
>
>
> Cheers,
>
> Nick 
>
> On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
> Bittlingmayer wrote:
>>
>> Yes, it is the Flex Env.
>>
>> Reviewing the container build logs, it does not seem deterministic.  The 
>> total time varies, and the place in the process where multiple minutes pass 
>> between two log lines varies.
>>
>>
>> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform Support) 
>> wrote:
>>>
>>> Hey Adam,
>>>
>>> Are you deploying a Flexible Environment app? If so, what do the 
>>> container builder logs from the Console show as far as activity during this 
>>> time?
>>>
>>> Also, is this still occurring, or was it only for a certain period of 
>>> time? If it's transient, it might just be a momentary service degradation, 
>>> which for a Beta product is to be expected at this stage. When a product 
>>> goes into General Availability, we'll often have certain Service Level 
>>> targets in terms of latency, uptime, that you can rely on (for example, 
>>> read 
>>> here <https://cloud.google.com/compute/sla> for Compute Engine SLA's)
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
>>> Bittlingmayer wrote:
>>>>
>>>> Deployment with gcloud deploy app is slow (in the low dozens of 
>>>> minutes).
>>>>
>>>> The build is fast, it is the push steps that are slow.
>>>>
>>>> Both steps like Mounted from google_appengine/python and Updating 
>>>> service [test]...\ ie steps that are in the datacentre, not the upload 
>>>> itself.
>>>>
>>>> Thus the size of the code seems to have no effect, it is small enough 
>>>> in this case.  It happens with both python 2 and 3.
>>>>
>>>> Is there a way to increase an allocation to speed this up?  Are there 
>>>> other factors?
>>>>
>>>

-- 
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/e10adca8-0b3e-4cef-a121-7426c08fdbba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: deploy is very slow

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adam,

Could you capture the deployment logs using the flags "--verbosity debug" 
and "--log-http", piping this output into the "ts" utility to prepend a 
timestamp to each line, and then email me the logs? I'll be able to analyze 
what might be going on that way. On linux / Mac that will look like:

gcloud --quiet --verbosity debug --log-http app deploy app.yaml --version 
${VERSION} 2>&1 | ts | tee -a deploy_log.txt 


(tee is used so that you can still read the output as it hits the console, 
and note that you'll have to put whatever version you want in the command 
where ${VERSION} is written)

On windows, you can use powershell to run the same command line after 
creating the "ts" filter to prepend timestamps by running the following 
line:

filter timestamp {"$(Get-Date -Format s): $_"}


Cheers,

Nick 

On Saturday, February 4, 2017 at 2:30:00 AM UTC-5, Adam Mathias 
Bittlingmayer wrote:
>
> Yes, it is the Flex Env.
>
> Reviewing the container build logs, it does not seem deterministic.  The 
> total time varies, and the place in the process where multiple minutes pass 
> between two log lines varies.
>
>
> On Friday, 3 February 2017 12:40:25 UTC-8, Nick (Cloud Platform Support) 
> wrote:
>>
>> Hey Adam,
>>
>> Are you deploying a Flexible Environment app? If so, what do the 
>> container builder logs from the Console show as far as activity during this 
>> time?
>>
>> Also, is this still occurring, or was it only for a certain period of 
>> time? If it's transient, it might just be a momentary service degradation, 
>> which for a Beta product is to be expected at this stage. When a product 
>> goes into General Availability, we'll often have certain Service Level 
>> targets in terms of latency, uptime, that you can rely on (for example, read 
>> here <https://cloud.google.com/compute/sla> for Compute Engine SLA's)
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
>> Bittlingmayer wrote:
>>>
>>> Deployment with gcloud deploy app is slow (in the low dozens of 
>>> minutes).
>>>
>>> The build is fast, it is the push steps that are slow.
>>>
>>> Both steps like Mounted from google_appengine/python and Updating 
>>> service [test]...\ ie steps that are in the datacentre, not the upload 
>>> itself.
>>>
>>> Thus the size of the code seems to have no effect, it is small enough in 
>>> this case.  It happens with both python 2 and 3.
>>>
>>> Is there a way to increase an allocation to speed this up?  Are there 
>>> other factors?
>>>
>>

-- 
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/90bf7f8d-c218-4d09-bfdf-165cc94af818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: deploy is very slow

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Adam,

Are you deploying a Flexible Environment app? If so, what do the container 
builder logs from the Console show as far as activity during this time?

Also, is this still occurring, or was it only for a certain period of time? 
If it's transient, it might just be a momentary service degradation, which 
for a Beta product is to be expected at this stage. When a product goes 
into General Availability, we'll often have certain Service Level targets 
in terms of latency, uptime, that you can rely on (for example, read here 
 for Compute Engine SLA's)

Cheers,

Nick
Cloud Platform Community Support

On Thursday, February 2, 2017 at 9:02:29 AM UTC-5, Adam Mathias 
Bittlingmayer wrote:
>
> Deployment with gcloud deploy app is slow (in the low dozens of minutes).
>
> The build is fast, it is the push steps that are slow.
>
> Both steps like Mounted from google_appengine/python and Updating service 
> [test]...\ ie steps that are in the datacentre, not the upload itself.
>
> Thus the size of the code seems to have no effect, it is small enough in 
> this case.  It happens with both python 2 and 3.
>
> Is there a way to increase an allocation to speed this up?  Are there 
> other factors?
>

-- 
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/2f187450-c774-4478-9fbc-a008060d7b6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Make local appengine use remote datastore (Python)

['Nick (Cloud Platform Support)' via Google App Engine]

This is just an update for anybody who finds this thread and isn't quite 
sure how to integrate the fix above. I've written an example python app 
that can be run in the devserver environment to connect to the remote 
datastore. Be aware that this will likely require you to have installed 
google-api-python-client on your system with pip beforehand.


import time
import webapp2
from google.appengine.ext import ndb

class EpochStamp (ndb.Model):
t = ndb.IntegerProperty()



from google.appengine.ext.remote_api import remote_api_stub
from google.appengine.api import apiproxy_stub_map

local_urlfetch_stub = apiproxy_stub_map.apiproxy.GetStub('urlfetch')

def configure_remote_api_dev_safe (host):
remote_api_stub.ConfigureRemoteApiForOAuth(
host,
'/_ah/remote_api')
apiproxy_stub_map.apiproxy.ReplaceStub('urlfetch', local_urlfetch_stub)


def configure_remote_api_dev_unsafe (host):
remote_api_stub.ConfigureRemoteApiForOAuth(
host,
'/_ah/remote_api')



class MainHandler(webapp2.RequestHandler):
def get(self):
app = self.request.get('app')
configure_remote_api_dev_safe ('{}.appspot.com'.format(app))
# configure_remote_api_dev_unsafe ('{}.appspot.com'.format(app))
   

e = EpochStamp(t=int(time.time()))
e.put()
self.response.write('Inserted.')

app = webapp2.WSGIApplication([
('/', MainHandler)
], debug=True)
















On Wednesday, March 16, 2016 at 3:23:56 PM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Here's the link to the thread 
> <https://code.google.com/p/googleappengine/issues/detail?id=12835=12835=1458156144#makechanges>,
>  
> it should see replies shortly. Cheers!
>
> On Tuesday, March 15, 2016 at 8:29:38 PM UTC-4, Danny Tran wrote:
>>
>> Sure thing, and sorry about being off-topic. 
>>
>> Please let me know the public issue tracking link/number when you get 
>> around to it. 
>>
>> Thanks :)
>>
>> On Tuesday, March 15, 2016 at 4:39:23 PM UTC-5, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Danny,
>>>
>>> Thanks for your detailed analysis. I was proceeding with attempting to 
>>> get the code into a reproducing example, and your latest post and deep 
>>> reporting of the information has been a model of how to report an issue. 
>>> While this thread is technically off-topic here and should be in the Public 
>>> Issue Tracker, I'll handle cross-posting the information you've provided 
>>> there from this point on. 
>>>
>>> Thanks again for your excellent reporting and analysis!
>>>
>>> Sincerely,
>>>
>>> Nick
>>> Cloud Platform Community Support
>>>
>>> On Tuesday, March 15, 2016 at 4:16:34 PM UTC-4, Danny Tran wrote:
>>>>
>>>> Ok, I think I figured out the issue.
>>>>
>>>> ConfigureRemoteApiForOAuth replaces the stub for ALL services. 
>>>>
>>>> This includes the "urlfetch" service.
>>>>
>>>> The problem is the httplib2 library uses "urlfetch" when it detects 
>>>> google appengine.
>>>>
>>>> So using urlfetch in your app, results in a call to rpc.check_success() 
>>>> which results in another call to "urlfetch" and so on ad infinitum.
>>>>
>>>> One workaround I have is to replace the 'urlfetch' stub with it's 
>>>> original value after configuring the the remote api for oauth.
>>>>
>>>> from google.appengine.ext.remote_api import remote_api_stub
>>>> from google.appengine.api import apiproxy_stub_map
>>>>
>>>>
>>>> local_stub = apiproxy_stub_map.apiproxy.GetStub('urlfetch')
>>>> remote_api_stub.ConfigureRemoteApiForOAuth('myapp.appspot.com',
>>>> '/_ah/remote_api')
>>>> apiproxy_stub_map.apiproxy.ReplaceStub('urlfetch', local_stub)
>>>>
>>>>
>>>> This prevented the infinite recursion.
>>>>
>>>> I'm curious if there is a way to disable urlfetch from using google 
>>>> appengine built in that I am missing.  Either way, the documentation on 
>>>> making an app use the remote api does not mention anything about the 
>>>> urlfetch service recursion issue.
>>>>
>>>> Hope this helps someone.
>>>>
>>>>
>>>> On Thursday, March 10, 2016 at 10:32:32 AM UTC-6, Danny Tran wrote:
>>>>>
>>>>> I'm attempting to make my appengine application running locally use a 
>>>&

[google-appengine] Re: Memcache with nodejs ?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Pyang,

The Memcache service on App Engine will be accessed through a totally 
different lib/package than any access you may wish to make to a Redis 
 cluster. You might consider writing a simple service / 
class that will abstract calls to a get/set key-value service such that you 
can change its internal implementation by connecting to either Memcache or 
Redis, while the rest of your code can remain the same regardless.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, January 11, 2017 at 4:04:02 AM UTC-5, Pyang djo wrote:
>
> Adam,
>
> Thanks for the info and the form for memcache access.
>
> I have a newbie question - I can use same memcache lib/package with redis 
> and memcache ? am I right. I intend to make use of GAE memcache when its 
> enabled but I would like to go ahead and use redis now ? 
>
> Thank you,
>
>
> regards,
>
> On Tuesday, January 10, 2017 at 5:57:44 PM UTC, Adam (Cloud Platform 
> Support) wrote:
>>
>> Currently Memcache as a service is only available on the standard 
>> environment, but elsewhere in the docs 
>> ,
>>  
>> you can find mention of the early access form for Memcache on the flexible 
>> environment:
>>
>> The Memcache service is currently not available for the App Engine 
>> flexible environment. An alpha version of the memcache service will be 
>> available shortly. If you would like to be notified when the service is 
>> available, fill out this early access form 
>> .
>>
>> So yes, it is on the horizon. Note that the early access is for testing 
>> only and is not recommended for production applications.
>>
>> On Tuesday, January 10, 2017 at 11:46:21 AM UTC-5, Pyang djo wrote:
>>>
>>> Hi,
>>>
>>> Are there plans to make memcache available for nodejs on google app 
>>> engine itself (like for others Go,java,python,php) ??
>>>
>>> Currently they are suggesting to use external service - Redis Labs.
>>>
>>> Can anybody please comment on this  
>>>
>>> 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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b22947dc-ae4a-46f1-8255-a4996336d91c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Securing access between GAE applications

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Attila,

It's exactly to get those docs updated that we've taken notice of this. 
Thanks for linking that doc.

Cheers,

Nick
Cloud Platform Community Support

On Saturday, January 7, 2017 at 2:19:18 AM UTC-5, Attila-Mihaly Balazs 
wrote:
>
> It is partially documented here: 
> https://cloud.google.com/appengine/docs/python/outbound-requests#request_headers
>  
> (though it doesn't make it clear that headers are also stripped when the 
> request is coming from outside of GAE or when using sockets for example).
>

-- 
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/300fd915-cabb-4269-a5ca-fa7f7379495f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Securing access between GAE applications

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Mateusz,

Yes, this header will be stripped if present from an external source. I've 
just verified this now. It must be a "slip of the pen" that the docs don't 
mention this explicitly. I'll make sure that we get that updated.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, January 4, 2017 at 5:36:07 PM UTC-5, Mateusz Haligowski wrote:
>
> That sound like a great idea, but does AppEngine guarantees that there is 
> no way to spoof the header? I can always just make a curl request with the 
> header set, and the project id is also a part of the URL, isn't it?
>
> W dniu środa, 4 stycznia 2017 13:06:01 UTC-8 użytkownik Evan Jones napisał:
>>
>> You can check the X-Appengine-Inbound-Appid header on requests coming it 
>> to your service. On App Engine, it will be set by Google, so you can trust 
>> it. Check that it matches the project(s) you expect, and return some HTTP 
>> error if it doesn't match. See:
>>
>> https://cloud.google.com/appengine/docs/go/appidentity/
>>
>>
>>
>> On Wednesday, January 4, 2017 at 2:39:13 PM UTC-5, Mateusz Haligowski 
>> wrote:
>>>
>>> Hi google-appengine,
>>> I started playing with GAE a couple of weeks ago and absolutely love it. 
>>> I created a bunch of REST services with Go and deployed them to GAE. I've 
>>> also created a webapp that talks to my backend services.
>>>
>>> Now, I want to handle the user authentication with Auth0 on the webapp 
>>> side, and came to realization that my backend services are publicly 
>>> available. My question is: what is the approach to secure them? Is there 
>>> any way to tell GAE "Accept only http(s) calling from other GAE services?".
>>>
>>> Thanks,
>>> Mateusz
>>>
>>

-- 
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/e562cc8a-d146-4df1-8afe-dd45b8c9154e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine to Compute Engine communication via internal IP

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Jitenda,

The Flexible Environment can be used by any user, although of course being 
a beta product, it isn't covered by the same SLA's as other products. You 
should check our documentation including the terms of service 
, service level agreements 
, and the explanation of launch stages 
.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, December 29, 2016 at 9:14:50 AM UTC-5, JITENDRA GANGWAR wrote:
>
> Thanks Adam for your answer , But  as per this documentation 
>  App Engine flexible 
> environment is still in beta release , can it be used in production ?
>
> On Saturday, June 25, 2016 at 2:38:46 AM UTC+5:30, Adam (Cloud Platform 
> Support) wrote:
>>
>> You should be able to do this if you use a Flexible Environment instance, 
>> and specify the same network name 
>> 
>>  
>> in the app.yaml that your Compute Engine instance running MySQL is on. It 
>> won't work for Standard Environment instances as they are on separate, 
>> physical networks.
>>
>> I say "should" as I haven't played around with this, and there's an 
>> additional layer of network routing from the Docker container the app lives 
>> in which also has its own local subnet.
>>
>> On Friday, June 24, 2016 at 10:43:29 AM UTC-4, Stephen Dunkley wrote:
>>>
>>> I have a Java Web application deployed on a Compute Engine instance 
>>> connecting to MySql running on another Compute Engine instance in the same 
>>> project. I am able to connect to MySql using the internal IP address 
>>> (jdbc:mysql://10.240.0.4:3306/).
>>>
>>> If I deploy the same web application to an App Engine instance within 
>>> the same project, I can only connect to the MySql instance via the extermal 
>>> IP address (jdbc:mysql://104.196.148.141:3306/>>
>>> If I try to use the internal IP address, I get a Communication Link 
>>> Failure, Permission Denied due to policy.
>>>
>>> My question is how do I open up communication between an App Engine 
>>> instance and a Compute Engine instance via an internal IP address? The 
>>> performance is about 5 x faster when using the internal IP address.
>>>
>>> Any help would be much appreciated
>>>
>>

-- 
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/b259530c-7bde-4859-b4f0-c48aad9eaccf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Does anyone else also run into high latency problem connecting to Cloud Sql?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Andy,

Glad to hear it's being tracked. That would be the correct place to follow 
up for updates.

Cheers,

Nick
Cloud Platform Community Support

On Thursday, December 29, 2016 at 11:07:21 PM UTC-5, Andy Tseng wrote:
>
> Hey Nick,
>
> So Adam (also from Cloud Platform Support) was able to reproduce the 
> problem. It seems like it has something to do with the location of the 
> project. My whole project is located at asia-northeast1 so it probably has 
> something to do with that location not being able to run socket connection 
> fast enough. If you also have any updates, please let me know. Thank you!
>
> On Thursday, December 29, 2016 at 10:53:37 AM UTC+8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Andy,
>>
>> Thanks for that information. I'm currently working on reproducing the 
>> behaviour, although I'm not seeing it so far. It may be related to the App 
>> Engine app's location. Are you sure your app's instances are in 
>> asia-northeast1? 
>>
>> Also, this is speculation and I'll have to confirm, but perhaps there's 
>> something odd happening with the resolution of the SQL instances' location 
>> / routing of packets when using the unix socket (which is of course an 
>> abstraction rather than a mere socket to a db process running on the local 
>> "machine") while the more direct IP route is avoiding that. 
>>
>> I'll get back to you as soon as I can with more clarity on this. In the 
>> meantime, it's good to know the IP workaround is efficient.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Friday, December 23, 2016 at 3:11:43 AM UTC-5, Andy Tseng wrote:
>>>
>>> Hey Nick, 
>>>
>>> Sorry for the late reply, both my CloudSQL and App Engine are in the 
>>> same project, which is located in northeast-asia. I am connecting through 
>>> PHP using mysqli, and I've tried PDO and I am getting the same result. 
>>> Interestingly, when I connect through host:port, I am getting a lot lower 
>>> latency. I have whitelisted 0.0.0.0/0 for IP and using host:port 
>>> connection and I am getting a pretty low latency (I know it's not secure). 
>>> Which is weird, because unix socket should be a lot faster. Here is my code 
>>> for both type of connection:
>>>
>>> YAML :
>>>
>>> MYSQL_DSN: /cloudsql/projectname:asia-northeast1:instancename 
>>> MYSQL_USER: user
>>> MYSQL_PASSWORD: password
>>> MYSQL_DATABASE: dbname
>>>
>>>
>>> Using socket:
>>>
>>>
>>> $servername = getenv('MYSQL_DSN');
>>> $username = getenv('MYSQL_USER');
>>> $password = getenv('MYSQL_PASSWORD');
>>> $dbname = getenv('MYSQL_DATABASE');
>>> $connection = new mysqli(null, $username, $password, $dbname, null, 
>>> $servername);
>>>
>>>
>>> Using host:port  :
>>>
>>> $servername = "ip.address:port";
>>> $username = getenv('MYSQL_USER');
>>> $password = getenv('MYSQL_PASSWORD');
>>> $dbname = getenv('MYSQL_DATABASE');
>>> $connection = new mysqli($servername, $username, $password, $dbname);
>>>
>>>
>>> Please let me know if you can tell what's wrong! Thank you very much.
>>>
>>> On Wednesday, December 21, 2016 at 5:39:43 AM UTC+8, Nick (Cloud 
>>> Platform Support) wrote:
>>>>
>>>> Hey Andy,
>>>>
>>>> Let us know if you can get some of those details to us. We'd be happy 
>>>> to take a look into further investigating a possible cause.
>>>>
>>>> Cheers,
>>>>
>>>> Nick
>>>> Cloud Platform Community Support
>>>>
>>>> On Wednesday, December 14, 2016 at 8:47:06 AM UTC-5, Andy Tseng wrote:
>>>>>
>>>>> So I am connecting to Second Gen Cloud SQL from my App Engine, and 
>>>>> both of them are in the same project. However, the latency is really 
>>>>> high, 
>>>>> up to 1.3 seconds. So I was wondering if anyone else is also running into 
>>>>> this problem. Everything works fine, but it's just the high latency and 
>>>>> the 
>>>>> same structure at AWS has a much shorter latency, so I was wondering why.
>>>>>
>>>>

-- 
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/167901dc-628d-4768-a5e2-34b38ce981de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to make Google appEngine plugin for Eclipse neon.2 work with Cloud SDK for Python in Windows.

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Vasan,

Could you post the specific error messages you're seeing, and provide some 
links to the documentation you're following to install the SDK?

I'll be glad to help once you send that information, as it will allow 
anybody who wants to help to more clearly understand the issue. I should 
mention that this post is about a specific issue for which you want 
one-on-one technical support, which is much better to direct to 
stackoverflow.com. That community is designed for this kind of interaction, 
while this forum (Google App Engine Groups forum) is meant for more general 
discussion of the platform and services, such as design patterns, etc.

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, December 28, 2016 at 9:08:03 AM UTC-5, Vasan Varadarajan 
wrote:
>
>
> After installing the plugin for Eclipse neon.2, I am unable to configure 
> the google app engine (Cloud SDK for Python). The error is 'Failed to 
> initialize App Engine SDK at C:\Program Files (x86)\Google\Cloud SDK' . I 
> downloaded the Cloud SDK into that location.
>
> I noticed that I was able to do this configuration if I download the Cloud 
> SDK for java.  The java SDK download is a zip file, whereas the python 
> download is thru the installer for windows.
>
> My Env: Windows 10, Eclipse neon.2, Cloud SDK
>
> Is there any updated documentation for 'Cloud SDK for Python' and the 
> Eclipse appEngine plugin for Windows?  
>

-- 
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/e51e1e83-1bbe-4529-b846-761452c7bb5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Does anyone else also run into high latency problem connecting to Cloud Sql?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Andy,

Thanks for that information. I'm currently working on reproducing the 
behaviour, although I'm not seeing it so far. It may be related to the App 
Engine app's location. Are you sure your app's instances are in 
asia-northeast1? 

Also, this is speculation and I'll have to confirm, but perhaps there's 
something odd happening with the resolution of the SQL instances' location 
/ routing of packets when using the unix socket (which is of course an 
abstraction rather than a mere socket to a db process running on the local 
"machine") while the more direct IP route is avoiding that. 

I'll get back to you as soon as I can with more clarity on this. In the 
meantime, it's good to know the IP workaround is efficient.

Cheers,

Nick
Cloud Platform Community Support

On Friday, December 23, 2016 at 3:11:43 AM UTC-5, Andy Tseng wrote:
>
> Hey Nick, 
>
> Sorry for the late reply, both my CloudSQL and App Engine are in the same 
> project, which is located in northeast-asia. I am connecting through PHP 
> using mysqli, and I've tried PDO and I am getting the same result. 
> Interestingly, when I connect through host:port, I am getting a lot lower 
> latency. I have whitelisted 0.0.0.0/0 for IP and using host:port 
> connection and I am getting a pretty low latency (I know it's not secure). 
> Which is weird, because unix socket should be a lot faster. Here is my code 
> for both type of connection:
>
> YAML :
>
> MYSQL_DSN: /cloudsql/projectname:asia-northeast1:instancename 
> MYSQL_USER: user
> MYSQL_PASSWORD: password
> MYSQL_DATABASE: dbname
>
>
> Using socket:
>
>
> $servername = getenv('MYSQL_DSN');
> $username = getenv('MYSQL_USER');
> $password = getenv('MYSQL_PASSWORD');
> $dbname = getenv('MYSQL_DATABASE');
> $connection = new mysqli(null, $username, $password, $dbname, null, 
> $servername);
>
>
> Using host:port  :
>
> $servername = "ip.address:port";
> $username = getenv('MYSQL_USER');
> $password = getenv('MYSQL_PASSWORD');
> $dbname = getenv('MYSQL_DATABASE');
> $connection = new mysqli($servername, $username, $password, $dbname);
>
>
> Please let me know if you can tell what's wrong! Thank you very much.
>
> On Wednesday, December 21, 2016 at 5:39:43 AM UTC+8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Andy,
>>
>> Let us know if you can get some of those details to us. We'd be happy to 
>> take a look into further investigating a possible cause.
>>
>> Cheers,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Wednesday, December 14, 2016 at 8:47:06 AM UTC-5, Andy Tseng wrote:
>>>
>>> So I am connecting to Second Gen Cloud SQL from my App Engine, and both 
>>> of them are in the same project. However, the latency is really high, up to 
>>> 1.3 seconds. So I was wondering if anyone else is also running into this 
>>> problem. Everything works fine, but it's just the high latency and the same 
>>> structure at AWS has a much shorter latency, so I was wondering why.
>>>
>>

-- 
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/c2e82b4b-f678-48f4-bf59-56ff8d785239%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 4 Instance spinning in 4 secs

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Rajesh,

The scaling behaviour on your app is highly dependent on the contents of 
your app.yaml / appengine-web.xml file. Could you post that? 

Also, it would be good to get a larger time-window selection of logs in 
text format (rather than screenshot) along with a screenshot of the 
instance numbers graph covering the same time period. This would be very 
helpful in reasoning about what is happening here.

If you have any further questions, feel free to send them along with your 
reply and I'll be glad to assist in answering them. 

Cheers,

Nick
Cloud Platform Community Support  

On Sunday, December 25, 2016 at 9:56:07 PM UTC-5, Rajesh Gupta wrote:
>
> Sorry, in 4 minutes (not 4 sec) there are 4 new instances.  You can see 
> that betwee 23:32 & 23:36.
>
> There are only 6-7 requests during that time.
>
> On Mon, Dec 26, 2016 at 7:57 AM, Rajesh Gupta <
> rajesh.gu...@veersoftsolutions.com> wrote:
>
>> Hello 
>> Following is the traffic to our website.  
>>
>> You can see suddenly, there are new four instances ('i' in the orange 
>> color denotes log.warning).  I do log.warning in my context listener.  
>> Between 23:32 & 23:36, ie 4 secs, there are new four instances.  The 
>> traffic could have well served with the normal instance.  Each of the 
>> instance spinning and serving is taking approx 22 sec.  
>>
>> This is a very bad experience to our users.
>>
>> Please suggest the recommended correct settings for low traffic website, 
>> so that instance spinning is not taking place.
>>
>>
>> 23:54:14.017GET200203 B132 msGooglebot 2/robots.txt
>> 23:54:12.571GET200203 B1.2 sGooglebot 2/robots.txt
>> 23:36:08.111POST20031.12 KB23.3 sChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.listProducts
>> 23:35:51.633POST200291 B22.6 sChrome 55
>> /_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction
>> 23:34:09.281POST20051.89 KB19.1 sChrome 55
>> /_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction
>> 23:33:10.557POST2003.49 KB1 sChrome 55
>> /_ah/spi/com.veersoft.services.api.ReportAPI.viewLedgerTransaction
>> 23:33:06.428POST2001.46 KB246 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.listBankCashAccounts
>> 23:32:40.392POST20031.12 KB463 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.listProducts
>> 23:32:11.464POST2008.87 KB26.5 sChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction
>> 23:31:56.158POST200644 B594 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction
>> 23:31:09.541POST2008.87 KB707 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction
>> 23:30:34.928POST2007.83 KB807 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction
>> 23:30:11.573POST20027.9 KB672 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.listCustomer
>> 23:29:55.646POST2005.01 KB692 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.viewCustomerTransaction
>> 23:29:18.924POST20027.9 KB928 msChrome 55
>> /_ah/spi/com.veersoft.services.api.MastersApiV3.listCustomer
>>
>>
>> -- 
>> Regards,
>> Rajesh
>> *www.VeersoftSolutions.com *
>> *www.GainERP.com *
>> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
>> Mobile*
>>
>>
>
>
> -- 
> Regards,
> Rajesh
> *www.VeersoftSolutions.com *
> *www.GainERP.com *
> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform and 
> Mobile*
>
>

-- 
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/2cc43cd5-7ef2-4e1c-9d54-819325eec656%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Mark,

Any update on my last questions? Did you make a post to the Public Issue 
Tracker or would you like to keep corresponding here?

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, December 6, 2016 at 6:41:40 AM UTC-5, Mark Cummins wrote:
>
> The new Python SDK (1.9.49) includes pycrypto update to 2.6.1.
>
> We've flipped over to the new library version, and we're now seeing errors 
> like this:
>
>
> 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
>  
> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.
> 11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>
>
> It looks like this is a platform problem with the new 1.9.49 SDK? Or are 
> we doing something to cause this?
>

-- 
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/89695daf-6078-4876-a5b5-0c1c55107be9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.