Re: [google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-13 Thread Nick (Cloud Platform Support)
Hey all, This issue was likely to be affecting multiple users. It was related to a change in the deployment pipeline to improve performance of deployments. One possible fix is to run: gcloud config set app/use_appengine_api True One could also attempt to use appcfg for deployment. If this is

Re: [google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-13 Thread Stefano Ciccarelli
We are experiencing the same issue on our java app: some parts of the app are missing. Il giorno mer 13 gen 2016 alle ore 15:57 Giuseppe Reina < giusep...@google.com> ha scritto: > We are currently investigating on few reports of this issue. As a > workaround you can either deploy via the old ap

[google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-13 Thread Giuseppe Reina
We are currently investigating on few reports of this issue. As a workaround you can either deploy via the old appcfg tool [1,2] or use gcloud by disabling the use_appengine_api flag, e.g. > gcloud config set app/use_appengine_api False Sincerely, Google Cloud Platform Support [1]: https://c

[google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-13 Thread Fahim ul Haq
I am seeing the exact same issue and just like Andreas, we didn't change anything in the appengine directory and have local test cases that all pass. I tried clearing the staging bucket as well and it didn't help. Here's very similar traceback. Traceback (most recent call last): File "/base/da

[google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-12 Thread Nick (Cloud Platform Support)
Can you attempt to check the python path during initialization (appengine_config.py) and also attempt to add the relevant "roger" directory? I know this is a sanity-check, but does roger/ contain an __init__.py file? Is it possible to check the size on disk of the versions against what the Ver

[google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-12 Thread Andreas Blixt
I'm still unable to get any further with this. I also tried emptying the staging bucket in Cloud Storage. The only real difference I can find is that App Engine v1.9.31 came out recently. On Tuesday, January 12, 2016 at 6:03:18 PM UTC-5, Andreas Blixt wrote: > > I've tried rebuilding the entire

[google-appengine] Re: New deploys suddenly fail to find local packages

2016-01-12 Thread Andreas Blixt
I've tried rebuilding the entire source directory from scratch and there is still no difference. What I do notice is that the App Engine Versions list claims my source changed from 9.8 MB to 5.3 MB which clearly is wrong when all that changed was a few lines of code. I'm starting to suspect this