Steven Buss Bacio

Sorry for not seeing this bug earlier. The good news is that this is an easy fix you can apply to your local `dev_appserver` instance. Edit lines 89-91 of `$(dirname...

Hi all, sorry that I missed this issue! I'll try to address everything, but if I miss something please let me know. First, hey @kevinburke! Thanks for your tool; I...

@leighmcculloch > If requests always had context's, inside and outside of appengine porting would probably be simpler, removing the need to do appengine.NewContext(r) since requests were built already with an...

@ejcx > logs didn't work. > I have lots of sanity checks to make sure my code has everything it needs when it starts in the init functions, otherwise it...

Go 1.13 does not support `google.golang.org/appengine`. It should work with Go 1.11 -- I second @juliehockett's recommendation to update gcloud. Your `dev_appserver.py` is probably out of date.

First guess is that cloudbuild is resource constrained so you need to increase the timeout. Try this: ```go inst, err := aetest.NewInstance(&aetest.Options{StronglyConsistentDatastore: true, StartupTimeout: 120 * time.Second}) ```

Edit: oh, we don't pass that timeout, and in fact don't even support it for standard. That 15s timeout is hardcoded... Is this an App Engine Standard or Flex app?...

I don't quite understand your question. Are you experiencing this issue when running locally or in production?

> I suggest that the docs [...] are changed to state that the recommended way to run an app in go111 is to call appengine.Main and use google.golang.org/appengine/log instead of...

I'm not quite sure I understand what you're trying to accomplish. Do you have control of the private key for the given public key? Here's a rough example of how...