[google-appengine] Re: App Engine Phishing Website

[Dan Babbitt]

Thank you Hector for your help and for escalating internally.

Our company is a Web Risk customer so we push URLs to Web Risk via API as 
opposed to the public facing website.

Would your team be open to possibly vetting my company for direct access to 
report Phishing Websites hosted on GCE or App Engine?

​Dan Babbitt

Director, Security Operations

Allure Security

877-669-8883 x717
https://www.alluresecurity.com/



On Friday, June 17, 2022 at 2:00:52 PM UTC-4 Hector Martinez Rodriguez 
wrote:

> The form you submitted is correct, but you can additionally use this one 
> <https://safebrowsing.google.com/safebrowsing/report_phish/> to report 
> the fraudulent clone. Nevertheless, we created an internal report to 
> escalate this concern too.
>
> On Thursday, June 16, 2022 at 4:58:18 PM UTC-5 dbab...@alluresecurity.com 
> wrote:
>
>> Hello,
>> I used the form 
>> <https://support.google.com/code/contact/cloud_platform_report> to 
>> report a phishing website 10 days ago and the site, while difficult to 
>> reach, is still publicly accessible.
>>
>> What can we do to escalate?
>>
>> IP address: 34.145.113.173
>> https://34.145.113.173/
>> *Hostname:* 173.113.145.34.bc.googleusercontent.com.
>>
>> That's a fraudulent clone of First Republic Bank's online banking website.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/42aab346-2078-4494-9361-6b9334ee77fdn%40googlegroups.com.

[google-appengine] App Engine Phishing Website

[Dan Babbitt]

Hello,
I used the form 
 to report a 
phishing website 10 days ago and the site, while difficult to reach, is 
still publicly accessible.

What can we do to escalate?

IP address: 34.145.113.173
https://34.145.113.173/
*Hostname:* 173.113.145.34.bc.googleusercontent.com.

That's a fraudulent clone of First Republic Bank's online banking website.


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2a0b704f-6721-4ccc-a84e-16284fb0555en%40googlegroups.com.

[google-appengine] Deploying with Dockerfile: error: Unable to locate package python3.8

['Dan Cogswell' via Google App Engine]

 

I am using this Dockerfile to deploy to App Engine Flexible environment:

FROM gcr.io/google-appengine/python
RUN apt-get -y update && apt-get -y upgrade\
&& apt-get install -y software-properties-common \
&& add-apt-repository -y ppa:ubuntugis/ppa \
&& add-apt-repository -y ppa:deadsnakes/ppa \
&& apt-get -y update && apt-get -y upgrade\
&& apt-get -y install python3.8 python3.8-distutils python3.8-venv \
   gdal-bin libgdal-dev python3-gdal  \ 
&& apt-get autoremove -y \
&& apt-get autoclean -y \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*

RUN virtualenv /env -p python3.8
ENV VIRTUAL_ENV /env
ENV PATH /env/bin:$PATH

etc.

I've been using this configuration for at least a year and deploy to GCP 
regularly. I haven't installed or updated any libraries and only changed 
some Python code. As of this Friday (1/21/2022) morning, when I try to 
deploy I'm getting these errors:

Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package python3.8
E: Couldn't find any package by glob 'python3.8'
E: Couldn't find any package by regex 'python3.8'
E: Unable to locate package python3.8-distutils
E: Couldn't find any package by glob 'python3.8-distutils'
E: Couldn't find any package by regex 'python3.8-distutils'
E: Unable to locate package python3.8-venv
E: Couldn't find any package by glob 'python3.8-venv'
E: Couldn't find any package by regex 'python3.8-venv'
The command '/bin/sh -c apt-get -y update && apt-get -y upgrade&& 
apt-get install -y software-properties-common && add-apt-repository -y 
ppa:ubuntugis/ppa && add-apt-repository -y ppa:deadsnakes/ppa && 
apt-get -y update && apt-get -y upgrade&& apt-get -y install python3.8 
python3.8-distutils python3.8-venvgdal-bin libgdal-dev python3-gdal 
 && apt-get autoremove -y && apt-get autoclean -y && apt-get 
clean && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
ERROR
ERROR: build step 0 "gcr.io/cloud-builders/docker" failed: step exited with 
non-zero status: 100

---
ERROR: (gcloud.app.deploy) Cloud build failed. Check logs at 
https://console.cloud.google.com/cloud-build/builds/d994e9d6-3c73-4cb8-b5af-6a186c229d3f?project=33114313460
 
Failure status: UNKNOWN: Error Response: [2] Build failed; check build logs 
for details

Thanks in advance for any help you can provide.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fbaba519-c2c7-4906-a42d-205a0d358f27n%40googlegroups.com.

[google-appengine] glcoud app deploy no longer uses Dockerfile

[Dan Cogswell]

I've got a python 3.6 application I deploy to the flexible environment. It 
uses a Dockerfile, which is in the same directory as app.yaml.

Last week, it was using the Dockerfile correctly. Now, when I gcloud app 
deploy, it looks like it's ignoring the Dockerfile and instead uploading 
all files to Google Cloud Storage, just like it does in the standard 
environment. I believe I updated gsutil and or/gcloud last week. I'm on 
ubuntu 18.04.4 LTS

Is there something in the new gsutil that ignores the Dockerfile? I'm 
currently running:

> Google Cloud SDK 280.0.0
> alpha 2020.02.07
> app-engine-python 1.9.88
> app-engine-python-extras 1.9.88
> beta 2020.02.07
> bq 2.0.53
> cloud-datastore-emulator 2.1.0
> core 2020.02.07
> gsutil 4.47
> kubectl 2020.02.07


Here's my Dockerfile:

> FROM gcr.io/google-appengine/python
> RUN apt-get update && apt-get install -y \
>   binutils \
>   gdal-bin \
>   python-gdal
> RUN virtualenv /env -p python3.6
> ENV VIRTUAL_ENV /env
> ENV PATH /env/bin:$PATH
> ADD requirements.txt /app/requirements.txt
> RUN pip install -r /app/requirements.txt
> ADD . /app
> CMD gunicorn -b :$PORT mysite.wsgi



Many thanks for any hlep,
Dan Cogswell

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/90fb9692-1a45-492a-851c-d320965465ad%40googlegroups.com.

[google-appengine] Gcloud App Deploy no longer uses Dockerfile

[Dan Cogswell]

I have a Python 2.7 Google App Engine in the flexible environment. I deploy 
it using a Dockerfile with the command Gcloud App Deploy. The Dockerfile is 
in the same directory as app.yaml.

Last week this was working fine. Now, it ignores the Dockerfile and deploys 
to google cloud storage as if it didn't have a Dockerfile and was in the 
standard environment. (I always stop the deploy now, fearing the worst.)

I recently upgraded gcloud. Current versions are:

> Google Cloud SDK 280.0.0
> alpha 2020.02.07
> app-engine-python 1.9.88
> app-engine-python-extras 1.9.88
> beta 2020.02.07
> bq 2.0.53
> cloud-datastore-emulator 2.1.0
> core 2020.02.07
> gsutil 4.47
> kubectl 2020.02.07


My Dockerfile is:

> FROM gcr.io/google-appengine/python
> RUN apt-get update && apt-get install -y \
>   binutils \
>   gdal-bin \
>   python-gdal
> RUN virtualenv /env -p python3.6
> ENV VIRTUAL_ENV /env
> ENV PATH /env/bin:$PATH
> ADD requirements.txt /app/requirements.txt
> RUN pip install -r /app/requirements.txt
> ADD . /app
> CMD gunicorn -b :$PORT mysite.wsgi



Any insights are appreciated.

- Dan Cogswell

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/28e3a516-e7ef-456b-943e-dd2f80f300aa%40googlegroups.com.

[google-appengine] Re: Outbound gRPC from AppEngine Standard Python 2.7

[Dan Massey]

To close this thread for future readers -- grpcio is a built in library 
that can be added through your app.yaml: 
https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27

On Friday, December 6, 2019 at 5:17:18 AM UTC-8, Dan Massey wrote:
>
>
> Hi all,
>
> I'm trying to connect from a Python 2.7 AppEngine Standard app to a gRPC 
> server. I've seen in a few places (including this group 
> <https://groups.google.com/d/msg/google-appengine/Yl7E0Ff7uH8/lxU5VInHBQAJ>) 
> that this should be possible.
>
> Unfortunately, I am unable to import grpc, due to an import error 
> (ImportError: cannot import name cygrpc).
>
> Two questions:
> 1) Should it be possible to send a request from GAE Standard to a gRPC 
> server?
> 2) If so, does anyone have a code snippet or example of how to do this?
>
> Thanks for your help
> Dan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/026ac93d-45be-432c-a258-b52aed0cb489%40googlegroups.com.

[google-appengine] Outbound gRPC from AppEngine Standard Python 2.7

[Dan Massey]

Hi all,

I'm trying to connect from a Python 2.7 AppEngine Standard app to a gRPC 
server. I've seen in a few places (including this group 
<https://groups.google.com/d/msg/google-appengine/Yl7E0Ff7uH8/lxU5VInHBQAJ>) 
that this should be possible.

Unfortunately, I am unable to import grpc, due to an import error 
(ImportError: cannot import name cygrpc).

Two questions:
1) Should it be possible to send a request from GAE Standard to a gRPC 
server?
2) If so, does anyone have a code snippet or example of how to do this?

Thanks for your help
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1bad826f-3ba0-402e-9b68-920af6d79d66%40googlegroups.com.

[google-appengine] Re: Oauth verification warnings

[Dan Briggs]

Got it, thanks for the quick response Julie. I just submitted it and can 
confirm that it did _not_ break :) Just wanted to be cautious. Thanks for 
your help.

On Friday, 5 July 2019 08:23:28 UTC-7, Julie (cloud platform support) wrote:
>
> Looking at your screenshot the warning seems typical when unverified 
> scopes are present however if the email does say that if the app is not 
> verified by August 18, 2019, it will be classified as unverified then I 
> suggest getting the submission done. 
>
> From the 3 warnings, "Use of this API scope will be restricted until it is 
> approved" "Use of this domain will be restricted until it is approved" and 
> "Because you've added a sensitive scope, your consent screen requires 
> verification by Google before it's published" I not found any evidence that 
> by submitting the verification, that the scope would not be able to be used 
> and the warning themselves do not seem to point to 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/edfbbc99-4156-42dc-8d31-7fa1ddb285c4%40googlegroups.com.

[google-appengine] Re: Oauth verification warnings

[Dan Briggs]

Thanks Julie.

Yes, you're right that the warnings don't explicitly say it will become 
unverified if we submit it for verification. Good point. But it does say 
that the API scope will be restricted until verified.To me, that sounds 
like we won't be able to use the scope anymore once we submit it. We're 
actively using this scope in production so that would break our app.

I'm hoping these are just generic warning messages that are always shown 
when adding a sensitive scope and it's not taking into account the info 
that was in the YouTube email.

On Thursday, 4 July 2019 10:50:14 UTC-7, Julie (cloud platform support) 
wrote:
>
> According to this document 
>  it is suggested 
> to go through verification before you launch a user-facing app. If you have 
> confirmed that you need to submit your application for verification and 
> cannot 
> skip the process , 
> you can go through the process with these steps 
> . If 
> you do not submit in time your app will become unverified  
> so if necessary I 
> suggest completing the process sooner then later as it can take some time 
>  to 
> be completed. 
>
> The 3 warnings provided do not indicate that your app will become 
> unverified  if you 
> submit for verification so if the email indicated a date on which the your 
> app will become unverified then submitting it early is best practice for 
> avoiding the app from becoming unverified. 
>
> Please check out the FAQ 
>  for more 
> information. 
>
> I hope you have found this information helpful. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d413c440-e92a-4e93-916f-132316919899%40googlegroups.com.

[google-appengine] Oauth verification warnings

[Dan Briggs]

I recently received an email from YouTube about an oauth change. Here's the 
gist of the email:
1. As of July 19th 2019, a YouTube scope we are using ("../auth/youtube") 
is classified as sensitive.
2. That means we need to get our app verified.
3. If our app is not verified by August 18, 2019, it will be classified as 
unverified.

Fair enough.

However, when I go to verify our app, there are a few warning messages that 
concern me.

They are concerning because we are actively using this scope in production 
and rely on it. The warning messages make it sound like the scope will stop 
working and our app will become unverified as soon as we submit the 
verification form.

On the oauth consent screen 
<https://console.developers.google.com/apis/credentials/consent>, I've 
added the YouTube scope we need ("../auth/youtube"). Now I see three 
warning messages:
1. A message next to the new scope that says "Use of this API scope will be 
restricted until it is approved"
2. A message next to our domain that says "Use of this domain will be 
restricted until it is approved".
3. A generic warning that says "Because you've added a sensitive scope, 
your consent screen requires verification by Google before it's published".

Here's an image <https://ibb.co/KNtsZLB> of these 3 warnings.

To me, this sounds like our app is going to break once we submit it for 
verification.

In the email from YouTube, they said the app won't become unverified until 
August 18, 2019. But these warnings make me think otherwise.

Is our app going to become unverified as soon as we submit it? If so, how 
do we avoid that?

Thanks in advance!

Dan


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b018426b-5c38-4647-aa1f-b6c89f389e0e%40googlegroups.com.

Re: [google-appengine] Re: Datastore export permission only

['Dan McGrath' via Google App Engine]

Thanks for the feedback Rajesh. I'm the product manager for Cloud 
Datastore, and want to note we agree with you. We're working through some 
implementation details for custom roles at the moment, and unfortunately 
don't have dates to share. It's definitely in our plans to make this 
available though.

Regards,
Dan

On Monday, December 17, 2018 at 10:18:43 PM UTC-7, Rajesh Gupta wrote:
>
> It is risky to give  the comple datastore.importExportAdmin for upcoming 
> or new engineers.  Even experienced engineer can make a mistake importing 
> instead of exporting.
> When is the permission “datastore.databases.export” supported for the 
> custom roles.
>
> Rajesh
> *www.GainERP.com <https://www.gainerp.com/>*
> *Field Service Software on Google Cloud Platform and Mobile*
>
>
> On Sat, Dec 15, 2018 at 6:22 AM 'Mohammad I (Cloud Platform Support)' via 
> Google App Engine > wrote:
>
>> Hello Rajesh,
>>
>> Thank you for the message. Usually by creating a custom role 
>> <https://cloud.google.com/iam/docs/creating-custom-roles#creating_a_custom_role>
>>  
>> certain permission can be assigned to users. You can get more details about 
>> IAM custom role here 
>> <https://cloud.google.com/iam/docs/understanding-custom-roles>. 
>> Unfortunately at this moment “datastore.databases.export” is not supported 
>> for custom roles. You can find detailed list of all permissions and support 
>> levels here 
>> <https://cloud.google.com/iam/docs/custom-roles-permissions-support#list_of_all_permissions_and_support_levels>.
>>  
>>
>>
>> On Friday, December 14, 2018 at 5:46:19 AM UTC-5, Rajesh Gupta wrote:
>>>
>>> any idea on how to setup a user with only datastore.databased.export 
>>> permission?
>>>
>>> On Wed, Dec 12, 2018 at 7:40 PM Rajesh Gupta <
>>> raj@veersoftsolutions.com > wrote:
>>>
>>>> Hello,
>>>> I am setting up a new user in the IAM.
>>>> I want only the datastore.databases.export  permission.
>>>>
>>>> I don't want the  ROLE datastore.importExportAdmin  
>>>>
>>>> Rajesh
>>>> *www.GainERP.com <https://www.gainerp.com>*
>>>> *Accounting/Inventory/Orders/Sales/Purchase on Google Cloud Platform 
>>>> and Mobile*
>>>>
>>>>
>>>>
>>> Rajesh
>>> *www.GainERP.com <https://www.gainerp.com>*
>>> *Field Service Software 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-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/2ecc601c-d61e-4d1f-b564-c089776a8f26%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/2ecc601c-d61e-4d1f-b564-c089776a8f26%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/749caae6-f0ae-4645-86a4-0e03857e30ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: SSL for Naked Domain on Existing Project

[Dan Stickel]

@Mohammad I, thanks for the response.  I think the screen capture shows
that we are already using Google managed security.  Everything is working
except the https://mydomain.com

www.mydomain.com, https://www.mydomain.com, mydomain.com ... all work and
end up on https://www.mydomain.com

Only https://mydomain.com does not work.

Given that, do you think your advice will still work?  Unfortunately, I
cannot use gcloud commands, as I use the original App Engine SDK, and will
lose access to the appcfg command if I overwrite it with the GCloud SDK (
https://cloud.google.com/appengine/docs/standard/python/download bottom of
page).  Is there another way to do this, or can you do it for me?



On Wed, Dec 12, 2018 at 10:05 PM 'Mohammad I (Cloud Platform Support)' via
Google App Engine  wrote:

> It is appearing the naked custom domain has already been mapped. You can
> verify that by running the GCLOUD command “gcloud app domain-mappings
> list”
> which
> should show the list of your domains, subdomains and their corresponding
> certificates or you can run the GCLOUD command “gcloud domains verify
> DOMAIN”
> 
> to verify your domain is registered as verified by Google Cloud Platform.
> After that you can upgrade to Google managed SSL certificates using the
> GCLOUD command “gcloud app domain-mappings update DOMAIN
> --certificate-management='AUTOMATIC'” following the instructions outlined
> here
> .
> If you are using your own SSL certificates you should follow the
> instructions outlined here
> .
> After that you should be able to redirect the naked domain to HTTPS on the
> naked domain.
>
> I have noticed that you have shared your personal information like
> “Project Id” and custom domain in this Google Groups post. I would advise
> you to take caution before sharing any personal or project specific
> information like these in any public forums as they can be used to harm
> your application.
>
>
> On Sunday, December 9, 2018 at 9:07:19 PM UTC-5, Devel63 wrote:
>>
>> We have an existing app engine project started a number of years ago.  It
>> serves managed security HTTPS on the www subdomain.
>>
>> [image: Custom_Domain.png]
>> At the time of creation, naked domains were not supported.  The
>> instructions
>> 
>>  only
>> cover how to do that for a new project, and don't work for an existing one.
>>
>> Following the clues in the instructions, we added the 4  records to
>> our DNS provider (a "new" requirement), and now the HTTP naked domain
>> redirects to HTTPS for www, which is good.  But we'd like it to do the same
>> thing for HTTPS on the naked domain, and that gets an ERR_CONNECTION_CLOSED.
>>
>>  We tried adding the naked custom domain via the console, but that
>> doesn't work because it's already at least partially mapped:
>>
>> [image: Custom_Domain_Step2.png]
>> What can we do to get the naked domain working with HTTPS?
>>
> --
> 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/XNefdPm_jkk/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/05a963c9-0e1b-4b45-83c5-d7fc1c9f646f%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAM_94%2BmN97zttnHwL8dxxLsMOeBg1dBMgZMY0hBXOCJL61xW0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: What's the timeout for Node cloud tasks handlers?

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

Hello,

As I understand the documentation confirm that "Automatic scaling services 
must finish before 10 minutes". Therefore, it seems that it will accept if 
the task falls in 2 minutes. You should get a better assistance in the 
Stack Overflow[1] since you have a technical issue and it will require some 
troubleshooting. 

There, you should receive help from the community fellow enthusiasts, and 
from Google engineers when you add a tag in your post according to the 
product where you require assistance, as you can check in our 
documentation[2]. Additionally, I suggest that you post some sample code 
and details regarding your application like deployment and settings.

[1] http://stackoverflow.com/
[2] https://cloud.google.com/support/docs/stackexchange






On Wednesday, November 14, 2018 at 1:25:07 PM UTC-5, Konrad Garus wrote:
>
> I have an application that does some work in background, using default 
> Cloud Tasks for scheduling/executing the process.
>
> I would like the job to be able to run for a few minutes, or at least 
> understand what the actual limitations are and what I can do about them.
>
> According to docs on Push Queues (which seem to be equivalent to the 
> modern Cloud Tasks?), the deadline is 10 minutes: 
> https://cloud.google.com/appengine/docs/standard/python/taskqueue/push/#the_task_deadline
> .
>
> However, my job seems to crash after 2 minutes. 115 seconds is fine, 121 
> seconds is a crash. The workload and resource consumption is the same in 
> all cases. The message is always the unhelpful "The process handling this 
> request unexpectedly died. This is likely to cause a new process to be used 
> for the next request to your application. (Error code 203)".
>
> According to docs on Node request handling, there is a 60-second timeout: 
> https://cloud.google.com/appengine/docs/standard/nodejs/how-requests-are-handled
> .
>
> What is the timeout in the end? Is it 1 minute, 2 minutes, or 10 minutes? 
> Is there anything I can do to change it, if I want my job to run for 5 or 
> 30 minutes?
>
>
> [image: crash.png]
>
>
>
>
>

-- 
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/a901662d-2d3b-4702-a4ad-8755e8dceb63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to connect to deploy meteor app

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

>
> Hello, 
>
> You should get a better assistance in the Stack Overflow[1] since you have 
> a technical issue and it will require troubleshooting. There, you should 
> receive help from the community fellow enthusiasts, and from Google 
> engineers when you add a tag in your post according to the product where 
> you require assistance, as you can check in our documentation[2]. 
> Additionally, I suggest that you post some sample code and details 
> regarding your application like deployment and settings.
>

[1] http://stackoverflow.com/
[2] https://cloud.google.com/support/docs/stackexchange 

-- 
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/cb7328de-cba8-427c-9db6-09786a8261e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Python 3.7 and Dajngo 2.x

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

Hello, 

You can get more details about the Cloud Datastore Client Libraries in the 
following link.

https://cloud.google.com/datastore/docs/reference/libraries#client-libraries-install-python
 

-- 
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/a85bac5e-c6d5-46d9-96a8-4657c9fdb2a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Does GAE support tags?

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

Hello,

It seems that this feature is not available at the time.

For further interaction, please address any comment regarding improvement 
in the Feature Request[1], because our product team engineering is tracking 
all the details there.

Thank you for your understanding.


[1] https://issuetracker.google.com/110507715




On Saturday, November 10, 2018 at 7:24:58 PM UTC-5, Henry Pan wrote:
>
> Good question,
>
> I was also wonder what's the best way to pass those billing info to 
> another app, such as Harvest ? ( 
> https://help.getharvest.com/api-v2/timesheets-api/timesheets/time-entries/ 
> )
>
> *Thanks + Happy Friday*
>
>
> *Henry Pan*
>
> DevOps Architect | Dito 
>
> henry@ditoweb.com | PHONE: (425) 802-3975
>
> [image: Dito Logo.png]
>
>
>
> On Thu, Nov 8, 2018 at 11:11 AM 'George (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hello Joshua, 
>>
>> Your latest specifications have been included in the same PIT issue 
>>  mentioned above, so you may 
>> monitor developments and fixes on the same thread. 
>>
>> -- 
>> 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/f433c9e0-93db-4dd6-ae95-e86789fc28c9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/97dfb180-7892-455b-8380-1761927ad2f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Not able to register for Google Cloud Platform Free Trial

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

Hello, 

It seems that our GCP engineering team is aware of this issue actively 
working on it. You can get updates on the progress of this fix by following 
the already mentioned issue tracker link[1]. 

The credit card information is required to confirm the identity"[2]and let 
us know that you are not a robot". Therefore, this issue should not close 
your account.

However, you can experience some issue if your free trial gets expired or 
if your application exceeds usage limits. Kindly note that, as eligible to 
a free trial on Google Cloud Platform, you will be allowed to explore our 
products for 12-months, respecting the limit of $300(credit Free Trial). 
You can find more detail regarding Google Cloud Platform Free Tier in the 
following FAQ link[3]

I hope this information has met your needs.

[1] https://cloud.google.com/free/docs/frequently-asked-questions

[2] 
https://cloud.google.com/free/docs/frequently-asked-questions#why-credit-card

[3]https://cloud.google.com/free/docs/frequently-asked-questions#free-tier


On Wednesday, November 14, 2018 at 1:25:34 PM UTC-5, Trav Shadows wrote:
>
> Yes. But even with EMV card, you get the notification - "This card does 
> not accept automatic payments" So while you do get in, they will close down 
> your account in a few months. I dont know how many months you'll get free 
> trial though
>
> On Friday, October 13, 2017 at 6:33:40 PM UTC+5:30, RAJ KUMAR wrote:
>>
>> You can use EMV Debit card of following banks.
>>
>> ICICI bank, HDFC bank,AXIS bank.I would like to suggest you to visit my 
>> blog for detail answer.
>>
>> Not able to register for Google Cloud Platform Free Trial offer using 
>> Debit card/Credit card? 
>> 
>>
>> On Thursday, September 7, 2017 at 6:41:51 PM UTC+5:30, Developer Coder 
>> wrote:
>>>
>>> Hi
>>> I want to open account in Google Cloud Platform so i have read the 
>>> documentation. When i open this 
>>> https://console.cloud.google.com/freetrial?page=0 and add the basic 
>>> detail.
>>> After that when i add detail in Payment Method and click on *Start my 
>>> free trial* button then it said *Invalid card detail try with another 
>>> card* and account is not activate. I have tried with *VISA* card and 
>>> *Master 
>>> Card*. So kindly please do some help that how to solve this issue? 
>>> I just want to know that credit card is required to open account in 
>>> Google Cloud Platform Or we can use Bank account number also to open 
>>> account on it?
>>>
>>> On Friday, April 7, 2017 at 6:49:54 PM UTC+5:30, Sarmistha Guha Thakurta 
>>> wrote:

 I was trying to register for the Free Trial of Google Cloud Platform. 
 However, after I filled up my data and credit card details, though My VISA 
 credit card was debited with $1 but I was shown an error "Transaction was 
 declined due to an Invalid Payment". I tried with AMEX card as well but 
 still the same error?
 #GoogleCloudPlatform #FreeTrial #GCP

>>>

-- 
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/5c580938-a60f-4746-b129-8c5deed14925%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Will App Engine Flex Environment ever support Memcache?

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

Hello,

It seems that the present screenshot does not prove that you were selected 
to use the Flex Memcache Alpha Service. You'll know if you were selected if 
you receive an email with the invitation. Thus, it's important to get 
attention to your spans filters. The invitation to earlier access should 
also give you access to participate in the product forum[1]. I hope this 
information has met your needs.

[1] https://groups.google.com/forum/#!forum/gae-flex-memcache-preview


On Saturday, November 10, 2018 at 7:24:12 PM UTC-5, William Hingston wrote:
>
> It appears I was accepted into the alpha at some point (I filled out the 
> form months ago)
>
> However I wasn't given any notification and I'm not able to find any 
> documentation on how to use memcache in my app. I can manually add and 
> remove keys from the web interface though.
>
> Attached a screenshot of memcache in my flexible app's dashboard.
>
> On Wednesday, 8 August 2018 03:33:49 UTC+9:30, Gopal Ashok wrote:
>>
>> Hi Joshua,
>> App Engine Memcache for Flex alpha is closed. 
>>
>> The current caching story for App Engine Flex is Cloud Memorystore (Beta) 
>> which currently supports Redis. We do plan to provide support for Memcache 
>> that can be accessed from Flex. We will have a closed alpha for this in 
>> late Q3\early Q4 timeframe. 
>>
>> If you need a managed memcache service one option is to use redislabs.
>>
>> https://cloud.google.com/appengine/docs/flexible/python/using-redislabs-memcache
>>
>> Thanks
>> Gopal
>>
>>
>> On Tuesday, July 24, 2018 at 3:29:40 PM UTC-7, Joshua Lyon wrote:
>>>
>>> Thanks for the reply. I signed up for both Memcache (Flex) and Could 
>>> Tasks alpha access several days/weeks ago and never heard anything back... 
>>> hence the reason I'm posting here to get clarification.
>>>
>>> It's unclear if some of these alphas are just not actually open yet, if 
>>> they aren't accepting new requests, if the request just got lost, or what's 
>>> going on. As such, I was hoping to get some clarification! :-D
>>>
>>

-- 
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/765bba08-fc47-4ea7-8de5-b72f701e1c96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Issue with Standard environment(Node.js) automatic scaling

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

Hello, 

Your instance will be scaled depending on the parameter limits first 
reached. 

If you have 5 concurrent requests, but reached the Max_pending_latency 
parameter, for example, then the instance will be scaled. Also, there are 
some standard values that can spawn your instances[1].

[1] https://cloud.google.com/appengine/docs/standard/nodejs/config/appref


On Saturday, November 10, 2018 at 7:25:12 PM UTC-5, Nikitha Kamath wrote:
>
> Thank you. This issue have been reported in Issue tracker.
>
> With the below scaling parameters, when will a new instance get spawned? I 
> mean will it depend on concurrent requests or CPU utilization or pending 
> latency or any other metrics?
>
> instance_class: F2
> automatic_scaling:
>   max_concurrent_requests: 10
>   max_idle_instances: 1
>   max_pending_latency: 300ms
>   min_idle_instances: 0
>   min_pending_latency: 30ms
>
>
> On Monday, November 5, 2018 at 7:08:54 PM UTC+5:30, Nikitha Kamath wrote:
>>
>>
>> Hi,
>>
>> A Node.js application is deployed in App engine standard environment. In 
>> the app.yaml, automatic scaling is chosen with values given below. However, 
>> when using 'gcloud app deploy', it gives this error : Unexpected 
>> attribute 'target_throughput_utilization' for object of type 
>> AutomaticScaling.What is the solution for this? Are we missing some 
>> values in app.yaml? Also when there are no incoming requests, the number of 
>> instances is always 2 instead of 0. Why is that?
>>
>> Thank you.
>>
>> runtime: nodejs8
>> instance_class: F2
>> automatic_scaling:
>>   max_concurrent_requests: 10
>>   target_throughput_utilization: 0.8
>> handlers:
>> - url: /.*
>>   secure: always
>>   redirect_http_response_code: 301
>>   script: auto
>>
>>

-- 
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/329e098b-462f-4261-900b-35797a85b00d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google App Engine Java deployment with gcloud skips almost all files

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

You can follow this example:

https://cloud.google.com/appengine/docs/standard/java/config/appref#automatic_scaling_min_pending_latency

On Monday, November 12, 2018 at 7:32:47 AM UTC-5, Attila-Mihaly Balazs 
wrote:
>
> There is a deploy.version paramter for the Maven goal: 
> https://cloud.google.com/appengine/docs/standard/java/tools/maven-reference#appenginedeploy
>
> Attila
>

-- 
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/18805071-f1dc-4e0a-84d8-5447dec679ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Clarifying App Engine, custom VPCs, and VPNs

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

Can an App Engine Flexible app use a custom VPC?

> You should be able to use VPC with App Engine Flex, as you can check in 
the following documentation[1]. You can config the network instance access 
by following the setup documentation[2].

Can an App Engine Flexible app use a shared VPC defined in another project?

> Unfortunately, it is not possible to share VPC, and you can confirm this 
limitation in the following section[3].

“In a service project, App Engine Flexible resources cannot participate in 
Shared VPC.”

Can an App Engine Flexible app use a Cloud VPN connection?

> Yes, since the App Engine flex uses the Compute Engine structure, you’re 
allowed to implement a VPN connection. You can find more details regarding 
the VPN connections in the following documentation[4], and the differences 
between App Engine Flex and Compute Engine in the following[5].

Can an App Engine Flexible app use a Cloud VPN connection set up in another 
project? If so, is that implemented with a shared VPC or peered VPCs?

>Yes, you can provide a connection between two App Engine application or 
projects by using VPC, as you can confirm in the following[6].

I hope that makes things clearer for you. In the meantime, if you have any 
additional comments, questions, or concerns about your issue don’t hesitate 
to reply as I would be happy to help you.

[1] https://cloud.google.com/vpc/docs/vpc

[2]
https://cloud.google.com/appengine/docs/flexible/nodejs/reference/app-yaml#network_settings

[3] https://cloud.google.com/vpc/docs/shared-vpc#ineligible_resources

[4] https://cloud.google.com/vpn/docs/concepts/overview

[5]
https://cloud.google.com/appengine/docs/the-appengine-environments#comparing_the_flexible_environment_to_compute_engine

[6] https://cloud.google.com/vpc/docs/vpc-peering#key_properties


On Wednesday, October 24, 2018 at 3:53:29 PM UTC-4, Mark Drummond wrote:
>
> Hello everyone. I am trying to understand the interaction of App Engine 
> apps, custom VPCs, and VPNs. After much googling and document reading I 
> still don't have a clear picture here.
>
>1. Can an App Engine Flexible app use a custom VPC?
>2. Can an App Engine Flexible app use a shared VPC defined in another 
>project?
>3. Can an App Engine Flexible app use a Cloud VPN connection?
>4. Can an App Engine Flexible app use a Cloud VPN connection set up in 
>another project?
>   1. If so, is that implemented with a shared VPC or peered VPCs?
>
> As you might guess, I'm wondering whether my App Engine Flexible apps can 
> communicate back to our head office over VPN, and if so how that is 
> implemented. Initial thought was peered VPCs to a VPC that has an attached 
> VPN but I found at least one note indicating that is not possible. Next 
> thought was a shared VPC but found at least one note that said that would 
> not work either (specifically with App Engine).
>
> - Mark
>
> The content of this message is subject to our e-mail confidentiality 
> policy.  
> Le contenu de ce message est assujetti à notre politique 
> en matière de confidentialité des courriels. 
> 

-- 
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/5ae82a5d-ebc9-4c5d-92e6-95894d84b1d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Clarifying App Engine, custom VPCs, and VPNs

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

Hello Mark, 

I'm studying your questions and I will answer by tomorrow.  

On Wednesday, October 24, 2018 at 3:53:29 PM UTC-4, Mark Drummond wrote:
>
> Hello everyone. I am trying to understand the interaction of App Engine 
> apps, custom VPCs, and VPNs. After much googling and document reading I 
> still don't have a clear picture here.
>
>1. Can an App Engine Flexible app use a custom VPC?
>2. Can an App Engine Flexible app use a shared VPC defined in another 
>project?
>3. Can an App Engine Flexible app use a Cloud VPN connection?
>4. Can an App Engine Flexible app use a Cloud VPN connection set up in 
>another project?
>   1. If so, is that implemented with a shared VPC or peered VPCs?
>
> As you might guess, I'm wondering whether my App Engine Flexible apps can 
> communicate back to our head office over VPN, and if so how that is 
> implemented. Initial thought was peered VPCs to a VPC that has an attached 
> VPN but I found at least one note indicating that is not possible. Next 
> thought was a shared VPC but found at least one note that said that would 
> not work either (specifically with App Engine).
>
> - Mark
>
> The content of this message is subject to our e-mail confidentiality 
> policy.  
> Le contenu de ce message est assujetti à notre politique 
> en matière de confidentialité des courriels. 
> 

-- 
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/6f3ae047-1dfd-4212-88e1-8adc98c62f5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 502 Bad Gateway on a PHP GAE Standard - no app logs

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

The quantity of instances deployed default is 2, the minimum of instances 
required is 1, as you can confirm in this link[1]. However, maybe only 1 
instance it will not be enough for ~5 users. It seems that by setting 2 
instances, could help you to solve this issue. You can retrieve more logs 
in your PHP instance by using the “Stackdriver Logging in App Engine apps”, 
such as errors surfaced from within the Nginx process, Nginx logs 
specifically for health checks. You can find more details in the following 
documentation[2]. 
[1]https://cloud.google.com/appengine/docs/flexible/python/reference/app-yaml#automatic_scaling
 
[2]https://cloud.google.com/appengine/articles/logging

On Wednesday, October 17, 2018 at 8:22:17 AM UTC-4, Maxime Lebastard wrote:
>
>
> Hi,
>
> We've got a Node Express app on a GAE standard instance. It calls a PHP 
> service on another GAE standard instance - through a server-to-server http 
> request. 
>
> Most of the time it works well, but since our first production deployment 
> we had a few (32 times) 502 Bad Gateway errors every day on that request.
>
> By looking to the trace logs:
>
>- I can see the NodeJS errors (getting a 502 response, throwing an 
>exception etc...), 
>- I can see a first log at 22:59:52.974 http_load_balancer WARN log 
>because a 502 error has been returned.  jsonPayload.statusDetail value is 
>"failed_to_connect_to_backend"
>- I can see a second log at 22:59:52.979 http_load_balancer WARN log 
>because a 502 error has been returned. jsonPayload.statusDetail value is 
>"response_sent_by_backend"
>
> But I can't see any trace on the PHP service. I checked the health calls 
> of the same timeframe for the PHP service, all the healthchecks return a 
> 200 OK.
>
> My guess is a network error from Google Cloud - or maybe a latency matter, 
> but is there a way I can diagnose and fix that ? What can be the causes of 
> a load balancer returning a Bad Gateway whereas the GAE instance is up and 
> running ?
>
> Max
>

-- 
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/1a6f54a6-4126-4204-8c77-0cc7dfdb5ca0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: using 3rd party libraries on GAE standard with Python

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

Hi,

It seems that you’re experiencing an issue regarding access 
permissions(Java:403) and maybe you have used a not supported library (459 
issue).

Kindly note that the Google Groups channel is designed to provide a free 
expression space to Google community rise discussions on different matters. 

I believe that your questions should get a better assistance in the Stack 
Overflow[1] since it is related to a technical issue. There, you should 
receive help from the community fellow enthusiasts, and from Google 
engineers when you add a tag in your post according to the product where 
you require assistance, as you can check in our documentation[2]. 
Additionally, you can post some details regarding your scaling setup, 
project config, and some code samples.


[1] http://stackoverflow.com/

[2] https://cloud.google.com/support/docs/stackexchange


On Wednesday, September 26, 2018 at 11:39:01 PM UTC-4, Dewey Gaedcke wrote:
>
> does anyone recognize these errors upon deploying a Golang project on Std.
>
> com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:459)\\n\\tat
>  
> com.google.gse.internal.DispatchQueueImpl$WorkerThread.run(DispatchQueueImpl.java:403)\\n\"",
> "  } ],",
> "  \"message\" : null",
> "}",
> "\t\tat 
> com.google.apps.framework.producers.PresentImpl.get(PresentImpl.java:29)",
> "\t\tat 
> com.google.apphosting.admin.flex.lib.dm.InsertDmDeploymentProducerModule.produceInsert(InsertDmDeploymentProducerModule.java:75)",
> "\tSuppressed: CriticalInputFailure: 
> com.google.apphosting.admin.flex.lib.dm.InsertDmDeploymentProducerModule.produceDoneOrFailedOperation
>  failed while trying to inject 
> @com.google.apps.framework.producers.PrivateVisibility(annotation=\"@com.google.apphosting.admin.flex.lib.dm.InsertDmDeploymentProducerModule$InsertDmOperation\",
>  
> module=com.google.apphosting.admin.flex.lib.dm.InsertDmDeploymentProducerModule.class)
>  com.google.apphosting.admin.flex.lib.dm.internal.proto.Operation",
> "\tSuppressed: 
> com.google.common.util.concurrent.UncheckedExecutionException: ",
> "\t\tat 
> com.google.apps.framework.producers.Present.checkSucceeded(Present.java:54)",
> "\t\tat 
> com.google.apphosting.admin.flex.resources.deployment.CreateResourcesProducerModule.produceBackendService(CreateResourcesProducerModule.java:128)",
> "\tSuppressed: CriticalInputFailure: 
> com.google.apphosting.admin.flex.resources.deployment.CreateResourcesProducerModule.produceDeployedRecord
>  failed while trying to inject 
> @com.google.apps.framework.producers.PrivateVisibility(annotation=\"@com.google.apphosting.admin.flex.resources.deployment.CreateResourcesProducerModule$NewBackendService\",
>  
> module=com.google.apphosting.admin.flex.resources.deployment.CreateResourcesProducerModule.class)
>  java.util.Optional"
>   ]
> }
>   }
>
>

-- 
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/53cd4a11-dfeb-4eca-adc3-068c10301927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Why in Google App Engine Always 11 secs of Latency coming only for the first requests?

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

Hi Steven,

I'm handling the case in private because I am investigating the case with 
the customer. As soon as we find a solution I will remove private 
information and set the case as public again.

Cheers

On Wednesday, September 5, 2018 at 5:08:09 PM UTC-4, Steren Giannini wrote:
>
> Dan, it seems that the issue is not public. Would you mind making it 
> public or keep the conversation in the public forum?
>
> On Mon, Sep 3, 2018, 08:08 'Dan S (Cloud Platform Support)' via Google App 
> Engine  wrote:
>
>> Hello,
>>
>> It seems that you have reported this issue in the Issue Tracker:
>> https://issuetracker.google.com/issues/113672643
>>
>> therefore, I'll be closing this issue in this channel an I will assist 
>> you through the mentioned link.
>>
>> On Sunday, September 2, 2018 at 1:51:12 PM UTC-4, Sudhanshu Gaur wrote:
>>>
>>> I found that
>>>
>>> This can be a caused when your application is still booting up or 
>>> warming up instances to serve the request and can be called as loading 
>>> latency. To avoid such scenarios you can implement health check handler 
>>> like readiness check so that your application will only receive traffic 
>>> when its ready
>>>
>>> That's why I checked in my Logs that readiness check is performed 
>>> sometimes around 1 sec and sometimes around 200 ms
>>>
>>>
>>> [image: google_cloud_logging.png]
>>>
>>>
>>> Can anyone please tell me is there anything wrong in warming up my 
>>> instances because I don't think cold boot time is causing this problem.
>>>
>>> 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/82c7b4a1-98ac-4496-8f50-ea7d2237ddd3%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/82c7b4a1-98ac-4496-8f50-ea7d2237ddd3%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d747d2bf-b917-4c17-843e-7a4e5a788012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Created multipul bucket from Client side and data can be readable and same client

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

Hello,

I understand that you’re experiencing an issue while creating folders in 
the Cloud Storage.

In order to fully understand and investigate your issue, please provide me 
with the following information:
1. Have you faced any error message? if yes, please provide me with the 
content of this message. This information will help me to launch my 
investigation with an accuracy.
2. What is your role in the project[1]? This information will help me to 
confirm that you have the proper permission to create folders in the Cloud 
Storage.
3. Please, provide more details about the API that you’re implementing? 
send me a link for the API documentation. This detail will provide an 
additional context to check for product limitation and similar issues.
4. Were you able to create a folder in the Cloud Storage before? If yes 
when this issue starts to happen? This information will help me to look for 
any global issue in the same time frame that could be affecting you.

I will be awaiting your reply to proceed.

[1]https://cloud.google.com/iam/docs/granting-changing-revoking-access




On Monday, September 3, 2018 at 5:44:20 PM UTC-4, Suman Jha wrote:
>
> Hi everyone, 
>
> We are working on an API which required individual folder (Folder name 
> should be input from client side) inside bucket and the data (Image) inside 
> the bucket folder can be easily readable. Now the problem which we are 
> facing is that we are not able to create such bucket which can create 
> individual folder from client side with readable data. Please hep us!   
>

-- 
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/45ef24b5-8276-4242-91f0-49299987429b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Why in Google App Engine Always 11 secs of Latency coming only for the first requests?

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

Hello,

It seems that you have reported this issue in the Issue Tracker:
https://issuetracker.google.com/issues/113672643

therefore, I'll be closing this issue in this channel an I will assist you 
through the mentioned link.

On Sunday, September 2, 2018 at 1:51:12 PM UTC-4, Sudhanshu Gaur wrote:
>
> I found that
>
> This can be a caused when your application is still booting up or warming 
> up instances to serve the request and can be called as loading latency. To 
> avoid such scenarios you can implement health check handler like readiness 
> check so that your application will only receive traffic when its ready
>
> That's why I checked in my Logs that readiness check is performed 
> sometimes around 1 sec and sometimes around 200 ms
>
>
> [image: google_cloud_logging.png]
>
>
> Can anyone please tell me is there anything wrong in warming up my 
> instances because I don't think cold boot time is causing this problem.
>
> 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/82c7b4a1-98ac-4496-8f50-ea7d2237ddd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unable to access one of my google cloud instance

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

Could you please alaborate more about your issue? Are you talking about 
Google Compute Engine? This information will help me to better understand 
your issue.

I have found this article regarding your error message that could be of any 
help:

https://serverfault.com/questions/823564/google-cloud-unable-to-connect-to-the-vm-on-port-22




On Wednesday, August 22, 2018 at 2:12:30 PM UTC-4, manoj kumar dash wrote:
>
> Hi All,
>
> After changing in the /*etc/sysconfig*/network-scripts/ifcfg-eth0 file i 
> am not able to access the instance. Every time i am getting  the response 
> as -> "We are unable to connect to the VM on port 22." . Can anybody help 
> me to make my instance up
>
> Regards
> Manoj
>

-- 
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/0975df06-0a3b-4c20-8659-1d2374f5486f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appcfg.py download_app fails silently

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

Hello,

you can run the appcfg.py download_app as documented in Downloading in your 
cloud Shell and after download the project you can just upload to some 
repository.
1. open the Cloud Shell (sole.cloud.google.com)
2. create a folder (mkdir myApp)
3. Input command line in the cloud shell as per docs 
(https://cloud.google.com/appengine/docs/standard/python/tools/downloading-source-code)

appcfg.py -A [YOUR_PROJECT_ID] -V [YOUR_VERSION_ID] download_app myApp

4. upload your files to your repo.


On Saturday, May 20, 2017 at 5:53:11 PM UTC-4, Lewis wrote:
>
>
> I'm trying to take a look at a Google App Engine project started by 
> another developer and deployed to the Google Cloud Platform. I have project 
> owner rights. When running appcfg.py -A [appID] -V  [version] download_app 
> [location] there are no errors, but no files come down. 
>
> 12:00 PM Host: appengine.google.com
> 12:00 PM Fetching file list...
> 12:00 PM Fetching files...
>
> If the appID is invalid, or the version is invalid appfcg.py displays an 
> error, 
>
> 12:00 PM Host: appengine.google.com
> 12:00 PM Fetching file list...
> Error 404: --- begin server output ---
> This application does not exist (project_id=u'invalid'). To create an App 
> Engine application in this project, run "gcloud app create" in your console.
>
> or
>
> 12:00 PM Host: appengine.google.com
> 12:00 PM Fetching file list...
> Error 400: --- begin server output ---
> Major version "123" does not exist.
>
> but when the appID and version are valid it simply downloads nothing. Any 
> suggestions?
>

-- 
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/24bab34a-bf1f-4725-8789-aae4809cddf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "The process handling this request has unexpectedly died... (Error Code 203)"

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

Hello Charles,

In fact, I understand this part of your issue, and I believe that there is 
a good answer from Nick. However, my concern and my answer concerns to the 
HTTP 500 server error displayed in your screenshots. Sorry for do not let 
this clear.

On Monday, August 6, 2018 at 8:54:35 PM UTC-4, Charles Batty-Capps wrote:
>
> I can look into this, but I'm not sure that you carefully read my post. 
> I'm getting a "process has died unexpectedly" error, NOT a "deadline 
> exceeded error".
>
> On Monday, August 6, 2018 at 2:13:27 PM UTC-7, Dan S (Cloud Platform 
> Support) wrote:
>>
>> There are many possible reasons to cause this kind of issues such as 
>> Slow-Loading Apps,
>> Performance Settings, Warmup Requests, Delays Associated with Logging
>> Delays Associated with UrlFetch… you can find more details about the root 
>> causes and how to avoid errors in the following documentation[1].
>>
>> Also note that while using Java, the runtime may not terminate the 
>> process, so this could cause problems for future requests to the same 
>> instance. “To be safe, you should not rely on the DeadlineExceededError, 
>> and instead ensure that your requests complete well before the time limit.” 
>> as per docs[2].
>>
>> [1] 
>> https://cloud.google.com/appengine/articles/deadlineexceedederrors#the-request-timer
>> [2]
>> https://cloud.google.com/appengine/docs/standard/python/how-requests-are-handled#specifying_a_request_deadline
>>
>>
>> On Sunday, August 5, 2018 at 7:56:04 PM UTC-4, Charles Batty-Capps wrote:
>>>
>>> Your post may have given me an idea, but the root cause isn't what you 
>>> think. We always use a REST framework for all our services (the latest 
>>> version of Jersey currently), so I am 100% certain an unexpected 
>>> application level exception results in a 500 error and the stacktrace is 
>>> logged by an Exception handler in Jersey. We never see anything in the logs 
>>> except for the process death error when this happens. 
>>>
>>> It stands to reason that maybe an exception is being thrown in the 
>>> Jersey layer before it reaches the HTTP layer, and somehow nothing is 
>>> logged in this case.
>>>
>>> I'll investigate options with Jersey. Maybe there's a thread pool that 
>>> needs reconfiguring or something.
>>>
>>>

-- 
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/111e4098-6255-4236-a1cc-0d45ee2728ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "The process handling this request has unexpectedly died... (Error Code 203)"

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

There are many possible reasons to cause this kind of issues such as 
Slow-Loading Apps,
Performance Settings, Warmup Requests, Delays Associated with Logging
Delays Associated with UrlFetch… you can find more details about the root 
causes and how to avoid errors in the following documentation[1].

Also note that while using Java, the runtime may not terminate the process, 
so this could cause problems for future requests to the same instance. “To 
be safe, you should not rely on the DeadlineExceededError, and instead 
ensure that your requests complete well before the time limit.” as per 
docs[2].

[1] 
https://cloud.google.com/appengine/articles/deadlineexceedederrors#the-request-timer
[2]https://cloud.google.com/appengine/docs/standard/python/how-requests-are-handled#specifying_a_request_deadline


On Sunday, August 5, 2018 at 7:56:04 PM UTC-4, Charles Batty-Capps wrote:
>
> Your post may have given me an idea, but the root cause isn't what you 
> think. We always use a REST framework for all our services (the latest 
> version of Jersey currently), so I am 100% certain an unexpected 
> application level exception results in a 500 error and the stacktrace is 
> logged by an Exception handler in Jersey. We never see anything in the logs 
> except for the process death error when this happens. 
>
> It stands to reason that maybe an exception is being thrown in the Jersey 
> layer before it reaches the HTTP layer, and somehow nothing is logged in 
> this case.
>
> I'll investigate options with Jersey. Maybe there's a thread pool that 
> needs reconfiguring or something.
>
>

-- 
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/5265000c-0922-49c0-8e15-4314ec94b265%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Service Control API request count too large

['Dan Ciruli' via Google App Engine]

(note -- we have opened a bug report here 
<https://b.corp.google.com/issues/109873579>. Anyone having similar issues 
should star the thread so proper weight be given on it. Thank you.

On Thursday, June 7, 2018 at 9:27:16 AM UTC-7, Dan Ciruli wrote:
>
> Can you tell me if you are using Python or Java?
>
> We will investigate immediately.
>
> On Wednesday, June 6, 2018 at 9:33:09 PM UTC-7, Thành Nguyễn Xuân wrote:
>>
>>  I'm using only Gae and Endpoint service . Here is my billing status .
>>
>>
>> <https://lh3.googleusercontent.com/-7RONXJjOW5o/Wxi0GsGKAuI/As8/LOrdcauAbtgp4CU2jKMt0NF4bATeYs4MwCLcBGAs/s1600/billing.png>
>> And api 
>>
>>
>> <https://lh3.googleusercontent.com/-vslfQwUKtUU/Wxi1A3uwz6I/AtU/PY0Kzy4D2-sMIPetzjenGLLstfc9jU8hwCLcBGAs/s1600/service%2Bcontrol%2Bapi%2B.png>
>>
>> How can i reduce instance hours ?
>>
>>

-- 
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/275b1f4a-203a-4f52-99de-3252eb3d57c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Service Control API request count too large

['Dan Ciruli' via Google App Engine]

Can you tell me if you are using Python or Java?

We will investigate immediately.

On Wednesday, June 6, 2018 at 9:33:09 PM UTC-7, Thành Nguyễn Xuân wrote:
>
>  I'm using only Gae and Endpoint service . Here is my billing status .
>
>
> 
> And api 
>
>
> 
>
> How can i reduce instance hours ?
>
>

-- 
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/a100720f-2023-4936-8ded-1dfa06f6d18c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine deploy fails during CPB100 training

[Dan Bikle]

2646b7dd687c0d61 
size: 2202*
*DONE*

*-*

*Updating service [quakes] (this may take several minutes)...failed.*
*ERROR: (gcloud.app.deploy) Error Response: [9]*
*Application startup error:*
*/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py:273: 
UserWarning: Matplotlib is building the font cache using fc-list. This may 
take a moment.*
*  warnings.warn('Matplotlib is building the font cache using fc-list. This 
may take a moment.')*
*Traceback (most recent call last):*
*  File "ingestapp.py", line 22, in *
*import google.cloud.storage as gcs*
*  File 
"/usr/local/lib/python2.7/dist-packages/google/cloud/storage/__init__.py", 
line 39, in *
*from google.cloud.storage.batch import Batch*
*  File 
"/usr/local/lib/python2.7/dist-packages/google/cloud/storage/batch.py", 
line 29, in *
*from google.cloud.exceptions import make_exception*
*ImportError: cannot import name make_exception*

*bikle101@cpb100-195004:~/training-data-analyst/CPB100/lab2b/scheduled$*
*bikle101@cpb100-195004:~/training-data-analyst/CPB100/lab2b/scheduled$*
*bikle101@cpb100-195004:~/training-data-analyst/CPB100/lab2b/scheduled$*
*bikle101@cpb100-195004:~/training-data-analyst/CPB100/lab2b/scheduled$*



*I'd welcome any tips on fixing this lab:*


*https://codelabs.developers.google.com/codelabs/cpb100-serverless-ingest/#0*


*Thanks, -Dan*

-- 
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/0da25cde-d954-4462-8147-21f7875f4949%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "www.custom-url.com is already mapped to a project" error when trying to point custom domain to App Engine app

[Dan Ciruli]

Evan -

Wow! This totally worked.

Thanks so much.

On Tuesday, November 21, 2017 at 3:39:05 PM UTC-8, Evan Kaminsky wrote:
>
> Hi Todu,
>
> Here are the steps I used to get it set up.
>
> 1) Go to 
> https://developers.google.com/apis-explorer/#search/admin%20api/appengine/v1/appengine.apps.domainMappings.create
> 2) Fill out the request form and enable OAuth2.0 - See the attached 
> screenshot "domainMappingsCreate_Instructions.png" 
> 3) Execute the command, which will require you to authenticate with Google
> 3) To enable Google's built-in SSL support (Optional): Select your 
> subdomain from the table in the attached screenshot 
> "enableManagedSecurity_Instructions.png," and click the "Enabled Managed 
> Security" button (which will be enabled if you haven't already selected it).
>
> It took a few minutes for the SSL to kick in but it works like a charm. 
>
>
> On Monday, November 20, 2017 at 11:22:14 PM UTC-6, todu wrote:
>>
>> Please provide detailed steps explaining this.  I am having to redirect 
>> to appspspot instead of domain mapping. Also dont want appengine and google 
>> apps getting messed.
>>
>

-- 
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/63e567e8-8ded-49b4-9598-7c6336d3316a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Latest gradle plugin release fails with ExplodeWarTask.preserve() error

[Dan Gravell]

Thanks for posting. I also experienced this, although strangely on a 
project that was last built and ran successfully in May... coming back to 
it today, any task I run gives this NoSuchMethodError.

This unfortunately also includes invoking the gradle wrapper task, so I had 
to:

- Comment out all my appengine plugin stuff in my build.gradle
- Then generate the wrapper

Then invoking commands with ./gradlew instead of plain gradle worked.

Dan


On Friday, September 22, 2017 at 9:25:33 PM UTC+1, Richard Perfect wrote:
>
> Hi,
>
> This is my first day learning Google App-Engine, but I got stuck for a 
> while on what looks to be a problem with the latest release of the Gradle 
> plugin.
>
> In the build.gradle example here 
> <https://cloud.google.com/appengine/docs/standard/java/tools/gradle?authuser=1>;
>  
> It seems the 1.3.3 release (from a few days ago on Sep 19th) gives me the 
> following error;
>
>
> C:\Projects\App-Engine-Gradle-Hello>gradlew compileJava
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file 'C:\Projects\App-Engine-Gradle-Hello\build.gradle' line: 23
>
> * What went wrong:
> A problem occurred evaluating root project 'App-Engine-Gradle-Hello'.
> > 
> com.google.cloud.tools.gradle.appengine.standard.ExplodeWarTask.preserve(Lorg/gradle/api/Action;)Lorg/gradle/api/tasks/Sync;
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
>
> BUILD FAILED
>
>
>
> But when I downgrade to one of the earlier releases e.g. 1.3.2 I don't get 
> this issue.
>
> It turns out that I was using an older version of Gradle and it seems that 
> there's a difference between 1.3.2 and 1.3.3 that now requires a Gradle 
> version of 3.+ instead of 2.x
>
> Updating my gradle wrapper version to 3.3 solved the problem.
>
> gradle wrapper --gradle-version 3.3
>
>
> Just posting in case this helps someone, and so hopefully Google search 
> finds this post for someone else.
>
> Complete stacktrace follows for search engine indexing.
>
>
> C:\Projects\App-Engine-Gradle-Hello>
> C:\Projects\App-Engine-Gradle-Hello>gradlew compileJava --stacktrace
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file 'C:\Projects\App-Engine-Gradle-Hello\build.gradle' line: 23
>
> * What went wrong:
> A problem occurred evaluating root project 'App-Engine-Gradle-Hello'.
> > 
> com.google.cloud.tools.gradle.appengine.standard.ExplodeWarTask.preserve(Lorg/gradle/api/Action;)Lorg/gradle/api/tasks/Sync;
>
> * Try:
> Run with --info or --debug option to get more log output.
>
> * Exception is:
> org.gradle.api.GradleScriptException: A problem occurred evaluating root 
> project 'App-Engine-Gradle-Hello'.
> at 
> org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
> at 
> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:177)
> at 
> org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
> at 
> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:182)
> at 
> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38)
> at 
> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:25)
> at 
> org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
> at 
> org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
> at 
> org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:540)
> at 
> org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:93)
> at 
> org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:42)
> at 
> org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
> at 
> org.gradle.initialization.DefaultGradleLauncher$2.run(DefaultGradleLauncher.java:124)
> at org.gradle.internal.Factories$1.create(Factories.java:22)
> at 
> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
> at 
> org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)
> at 
> org.gradle.initialization.D

Re: [google-appengine] Re: Endpoints custom authentication javascript?

['Dan Ciruli' via Google App Engine]

Marie -

You could also look at using Cloud Endpoints along with Firebase. Firebase
does allow for username/password auth and features mobile client libraries
for generating the JWTs.

https://cloud.google.com/endpoints/docs/frameworks/python/authenticating-users
or
https://cloud.google.com/endpoints/docs/frameworks/java/authenticating-users



On Jul 11, 2017 10:24 AM, "'George (Cloud Platform Support)' via Google App
Engine"  wrote:

Hello Marie,

You can create a custom authenticator for Endpoints, as detailed on the
"Interface Authenticator" documentation page
.
General authentication-related information for Endpoints is presented on
the "Authenticating Users" page
.

Let us know if this information addresses your concern. You are most
welcome to come back with more detailed questions.

-- 
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/ms
gid/google-appengine/89f3dc25-ce51-4d11-8792-36fec2a308f9%40googlegroups.com

.

For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJ6Lt0_9zE3KBDhkD7jDuGHrr3NLWfMLo527npo6VRO%2BC6VA-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

['Dan Ciruli' via Google App Engine]

We are investigating and will report back findings here.

On Jun 26, 2017 6:56 AM, "Þórir Gunnarsson" 
wrote:

> Hi
>
> This stopped being an issue for us after updating the backend to use
> Endpoints V2. We never really figured out exactly what caused the issue in
> the first place.
>
> ÞG
>
>
> On Monday, June 26, 2017 at 1:47:24 PM UTC, Teke Sawo wrote:
>>
>> I am experiencing the same issue.
>>
>> Do we find any solution?
>>
>> On Friday, March 31, 2017 at 3:07:18 PM UTC+3, Þó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/1af397de-0d94-4aec-b267-
> 597e9e6961ea%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJ6Lt08baTzM3mxFD7qZnhox%3DjwGp4o%3DGuwzB0bbOWDSBdp6vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Can't file bugs to issue tracker

[Dan Gaffey]

I am seeing the same issue when trying to submit an issue in Android Public 
Tracker > Applications...

On Sunday, June 4, 2017 at 2:29:34 PM UTC-4, natario wrote:
>
> I fear this might be a dumb question, but I am not able to report issues 
> to the issue tracker at issuetracker.google.com.
> I select a component (e.g. Public Trackers > Cloud Platform > Compute > 
> App Engine > Flexible), write down the issue, click create, and get a 
> message on top of the page saying:
>
> Error: The following field(s) have invalid values: must be a comma 
> separated list of issue IDs
>
> I have no idea why and where should I put a list of issue IDs. And I can't 
> report this issue through the official tracker because, you know.
> Is there something wrong on my side?
>
> Safari 9.0.3.
>
>

-- 
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/3c6dfe82-29e5-4ce8-b7c8-fe51def3a0a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Can't file bugs to issue tracker

[Dan Morris]

Same for me: 

Windows 7 Pro SP1 

Firefox 53.0.3 (32-bit)
Chrome 64-bit 58.0.1029.110

Component: Public Trackers > Cloud Platform > Developer Tools > Cloud SDK

Same error in both browsers.

https://issuetracker.google.com/u/0/issues/new?component=187143&template=800102


On Monday, June 5, 2017 at 10:04:02 AM UTC-4, George (Cloud Platform 
Support) wrote:
>
> Hello Natario and Nicola, 
>
> Reproduction fails in the exact situation you described. More detail is 
> needed: browser, OS, whatever you may think of relevance in this context. 
>

-- 
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/f52a4f39-6ba0-4deb-bd53-ed72883a7b6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Did App Engine update the datastore quota?

['Dan McGrath' via Google App Engine]

There is a display issue for the new pricing changes we are working to 
resolve.

Regards,
Dan

On Monday, July 4, 2016 at 3:24:53 AM UTC-6, Sunny Jerry wrote:
>
> Friendly ping since nobody can answer my question
>
> On Sunday, July 3, 2016 at 1:55:29 AM UTC+8, Kamran (Google Cloud Support) 
> wrote:
>>
>>
>>
>> On Saturday, July 2, 2016 at 1:04:16 PM UTC-4, Sunny Jerry wrote:
>>>
>>> Hi
>>>
>>> I've noticed that GAE's document said it will change the datastore quota 
>>> at July 1st (
>>> https://cloud.google.com/appengine/pricing#costs-for-datastore-calls), 
>>> makes it more clearly and easily to developer,.
>>> But today when I try to delete 1000 keys in datastore, it still cost 64 
>>> percent of my datastore write operations, and all quota items in quota page 
>>> seems not been updated as they said in documentation.
>>>
>>> Any ideas?
>>> 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/6d88ab91-48d9-4639-80f0-30a83c5331a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Datastore Pricing July 1st 2016

['Dan McGrath' via Google App Engine]

Hi Marcel,

I'm the PM for Cloud Datastore. Thanks for pointing out the issue on 
Charges this month, I've sent it on to Engineering to investigate why that 
page is incorrect and the inconsistencies between values.

As to storage costs, Datastore and BigQuery are very different systems with 
different performance goals, running in vastly different configurations to 
meet those goals. This means are underlying costs are different as well.

Regards,
Dan

On Tuesday, July 5, 2016 at 9:54:34 AM UTC-6, Marcel Manz wrote:
>
> It appears that the 'Charges this month' page (
> https://console.cloud.google.com/billing/unbilledinvoice) has not yet 
> been updated according the new pricing scheme.
>
> This page still lists 'Datastore Write Ops' and an estimated $ amount. It 
> should instead show the new billing ops like 'Datastore Entity Writes' and 
> similar.
>
> The dashboard as well as quota usage history are correctly showing the new 
> charges for us. Strangly though that there is an inconsistency between 
> 'Datastore Stored Data' amount from Quota Details (smaller value, matching 
> dashboard value) opposed to Quota History (larger value, according to which 
> charging is done). In our case the difference between these 2 values is 
> around 10%.
>
> Can Google please comment why these values are not the same?
>
> Regards
> Marcel
>

-- 
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/1f373cad-0835-495f-937c-37181cfcae03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How can I share files (HTML templates) between App Engine modules?

[Dan Dubois]

Thanks Nick,

Glad my question found the right location in the end.

I thought I would reply here just for completeness. I ultimately wanted to know 
how I can avoid file duplication in my own local repo when sharing application 
files between modules. The answer on StackOverflow suggests simlinking 
directories between modules is the only way to go. As Nick suggests I could 
store my file data in Cloud Storage or the datastore but I want to avoid the 
complexities of that.

I'll accept the StackOverflow answer unless anyone has a better suggestion.

Best wishes,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cf2921ab-69b8-4af9-b75d-47c0ac602aa7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] How can I share files (HTML templates) between App Engine modules?

[Dan Dubois]

Crossposting from StackOverflow in case anyone has a good solution:

http://stackoverflow.com/questions/33088104/how-can-i-share-files-html-templates-between-app-engine-modules

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/db3d8946-190b-40e6-a7ac-fc0401a7c555%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: My billing account google compute engine inexplicably been disabled

[Dan Stokeley]

Hi Raul,

A more direct link for billing support would be this one:
https://support.google.com/cloud/contact/cloud_platform_billing?hl=en&cfsi=bronze_contact&cfnti=6186161&cft=3

Regards,
Dan Stokeley
Cloud Billing Product Manager

On Monday, 15 June 2015 06:31:03 UTC-7, Ryan (Cloud Platform Support) wrote:
>
> Salutations Raul,
>
> You should contact our Billing team <https://cloud.google.com/contact/> and 
> select 'Other' from the drop down menu.
>
> On Saturday, June 13, 2015 at 2:44:47 PM UTC-4, Raul Obagi wrote:
>>
>>
>> Inexplicably without warning my google compute engine billing account was 
>> disabled, and I made more intense search and investigation
>>
>> I followed the steps as described so support page 
>> https://support.google.com/cloud/answer/3540854?hl=en (Disable or enable 
>> billing) in which they explain the following:
>> Enable billing
>>
>>
>>1. Sign in to the Google Developers Console.
>>2. From the *Select a project* drop-down list, select a project name.
>>3. In the upper right, select the *Settings* icon.
>>4. From the menu, click *Project billing settings*.
>>5. On the Billing page, click the *Enable billing* button.
>>
>> and the referred button "Enable button billing" to which they refer in 
>> step 5 does not appear, I find no way to enable it again.
>>
>> to rule out problems, I opened another account billing using the same 
>> credit card and my "instance" is activated but after a few minutes turns to 
>> disable my account billing again
>>
>> *Maybe I can be helpful with the following information:*
>>
>> Yesterday make a payment, there is a probability that is generated 
>> authentication problem with my main credit card?
>>
>> I completely solvent with my payments
>>
>> My situation is very urgent because my business depends on this server 
>> and now all my services are fallen
>>
>> thank you very much for 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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fafceef8-28f9-484c-8224-e73f13ea568b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Creating Unique Entities

[Dan Dubois]

Jeff,

Thanks for confirmation and all the extra background information.

Dan

On Tuesday, May 19, 2015 at 6:55:02 AM UTC+1, Jeff Schnitzer wrote:
>
> It isn't the other way 'round, no. This is pretty standard fare for all 
> distributed systems, including RDBMSes.
>
> Let's say you get a timeout error (on GAE or Oracle). Did the txn commit 
> or not? It's not clear; there was probably a network disconnect and you 
> can't assume it was before or after the commit. You don't know.
>
> The HRD was (last time I checked) documented to have some edge conditions 
> that would throw ConcurrentModificationException even when the txn commits. 
> I didn't find a similar statement on a casual search now; it would be nice 
> to have some clarification from Google on this, because it would make life 
> easier if CME was idempotently retry-able. Timeouts and whatnot can just be 
> raised to the user as long as they aren't frequent.
>
> On the other hand, successful commits are successful commits. You don't 
> need to wonder about that.
>
> If you work on distirbuted applications (and practically all apps are 
> these days), this should be mandatory reading: 
> http://en.wikipedia.org/wiki/Two_Generals%27_Problem
>
> Jeff
>
> On Mon, May 18, 2015 at 10:38 PM, Dan Dubois  > wrote:
>
>> Hi Jeff,
>>
>> I just wanted some clarification on the following statement:
>>
>> "HOWEVER, you have to take idempotence rather seriously. The "edge cases" 
>> of the datastore produce errors/exceptions. Errors can happen even if the 
>> underlying transaction committed successfully."
>>
>> Are you saying that datastore transaction API might return an error to us 
>> but actually commit anyway? I just hope that it's not also the other way 
>> around where the transaction API returns that everything is OK but actually 
>> doesn't commit!
>>
>> Dan
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/9b40bc26-1078-4e7f-bc73-7d292f9ec46c%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3a700a9a-2e55-4869-9452-544767247834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Creating Unique Entities

[Dan Dubois]

Hi Jeff,

I just wanted some clarification on the following statement:

"HOWEVER, you have to take idempotence rather seriously. The "edge cases" of 
the datastore produce errors/exceptions. Errors can happen even if the 
underlying transaction committed successfully."

Are you saying that datastore transaction API might return an error to us but 
actually commit anyway? I just hope that it's not also the other way around 
where the transaction API returns that everything is OK but actually doesn't 
commit!

Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9b40bc26-1078-4e7f-bc73-7d292f9ec46c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Creating Unique Entities

[Dan Dubois]

Hi Francis,

I think I understand exactly what you mean and it's an interesting edge case 
when designing the datastore transaction system.

Somehow within a transaction it needs to record that the 'put' method either 
expects the entity it is saving to already exist or not exists. What's more 
this logic needs to kick in only if earlier in the transaction a 'get' bothered 
to detect if the entity existed in the first place!

I hope the designers of the datastore considered this and am sure they have as 
I have not seen anything to suggest transactional integrity has ever been 
broken in my apps. I guess you are looking for confirmation though as the way 
the datastore's internals are described in various don't suggest the edge case 
is catered for.

Maybe you could write a test and run it a reasonable number of times to see if 
atomicity guarantees break. I would be interested in seeing the results.

Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3a95db7e-e123-4625-a7f2-916d9f627f23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Cloud Platform wants to hear from you

[Dan Ciruli]

Hi, Karl -

I'm Dan Ciruli, and I recently took over as Product Manager on Endpoints. I 
really appreciate your feedback. My team is currently looking at 
improvements that we’d like to make in the next version of Endpoints and 
your comments jibe with what I’ve been hearing from a lot of our users. We 
are working on both the developer experience as well as providing some 
features that help you with managing your API (controlling access, etc).

I would be interested in a follow-up conversation with you -- send me an 
email (my last name @google.com) and I’d like to set something up.

Thanks -

Dan
On Monday, April 20, 2015 at 7:38:45 PM UTC-7, Alistair Burrowes wrote:
>
> Hi,
>
> I would echo a lot of what Karl said.
>
> I would like to see more examples of complex usage of GAE and or managed 
> VMs. These are the kind of usages that more advanced developers might want. 
> Here are a few examples of things that I have figured out or want:
>
> - CI/CD set up, with dev/staging environments and one button deployments 
> to production. It was a pretty long process of trial and error to achieve 
> this.
>
> - a single page app with separate the web front end and the backend 
> (endpoints) modules. This was also tricky since endpoints live behind /_ah 
> which can't be routed away from the default application. I think separating 
> these out and their build processes is healthy separation of concerns.
>
> - integrating gulp build processes into GAE dev servers/build processes. 
> In my case I'm using gradle app engine plugin.
>
> - "ismorphic" javascript app, with server side rendering via something 
> like react (I assume this would be a managed VM running node js) that 
> speaks to endpoints, from both client side and the node js layer.
>
> Also I agree that more transparency on the roadmap/discussions on 
> direction would be really useful.
>
> For example the lack of java 8 on GAE is a concern of mine - 
> https://code.google.com/p/googleappengine/issues/detail?id=9537 . There 
> isn't any communication as to what the status of this is (note: AWS 
> beanstalk supports java 8).
>
> I love the minimal configuration/maintenance of the GAE sandbox, but I 
> need to know if a shift to managed VMs is the longer term direction for 
> java support. It is not clear when starting a new java project if I should 
> bet on GAE java sandbox being supported in the long term or just go with 
> java 8 on a managed VM. 
>
> Other than this, I have found GAE/GCP to be fantastic and I am really 
> happy with the different tools and quality of the libraries provided.
>
> On Thursday, April 16, 2015 at 3:37:31 AM UTC+10, Katie Ball (Google Cloud 
> Support) wrote:
>>
>> Hi,
>>
>> My name is Katie, and I am on the Google Cloud Platform technical support 
>> <http://cloud.google.com/support> team.
>>
>> This message is to Google Cloud Platform community members, especially if 
>> you are newer to GCP. I would like to know what our team can do to help you 
>> have a better and more enjoyable experience during the first days on GCP.
>>
>> Did you need technical support?  If so, I’d like to hear all about it.
>>
>> I’d also like to know:
>>
>>- 
>>
>>What did you find most difficult about the first-time user experience?
>>- 
>>
>>Where did you get stuck?
>>
>>
>> Please reply to the group with your answers or any ideas you have on how 
>> the technical support team can help new customers get familiar with GCP. 
>>
>> And as a thank you for the great ideas, we will be giving away support 
>> coupons worth $450 (equivalent to 3 months of silver support) to 5 lucky 
>> community members who post a response. Please make sure to reply before 
>> April 22nd. 
>>
>> Thanks for your insights, and cloud on!
>>
>> Katie
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5610bc4d-852b-4476-a10b-51574cb2e925%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: HTTP/2 Protocol Support

[Dan Dubois]

Wow. That's great! Interesting that https://*.appspot.com shows HTTP/2 and 
when I run it through CloudFlare it shows SPDY/3.1.

On Thursday, March 19, 2015 at 8:50:00 PM UTC, Greg Jones wrote:
>
> It does. 
> You can install this chrome-extension (
> https://chrome.google.com/webstore/detail/spdy-indicator/mpbpobfflnpcgagjijhmgnchggcjblin
>  
> ) and it will show if you're connected to a site with anything other than 
> plain-old-http.
> If you check it when on, say, https://apprtc.appspot.com/ it should add a 
> blue icon in the URL-bar and show "HTTP/2 enabled (h2-14)". green means 
> SPDY (appspot.com showed this until recently. you can see it now on 
> twitter.com). When it's red that means "quic" is involved.
>
> On Thursday, 19 March 2015 13:07:27 UTC, Dan Dubois wrote:
>>
>> Does App Engine support the HTTP/2 protocol?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/436c60d4-87fe-4676-ba6b-d86fa6e151b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cloud Billing is enabled but isn't propogated to App Engine project

[Dan Stokeley]

Thanks for the detailed feedback and screenshots. I've filed a bug with our 
engineering team on this issue, will update when I have more information. 

Regards,
Dan

On Friday, 20 March 2015 11:43:57 UTC-7, Rasmus Vernhamn wrote:
>
> Thank you, but the option isn't available. It seems the Cloud Project 
> doesn't recognize that this is an App Engine project somehow. See 
> screenshots below:
>
> Screenshot of the URL you linked: http://snag.gy/swskP.jpg
> Screenshot of "Billing & Settings" for *faulty *app: 
> http://snag.gy/qFuZR.jpg
> Screenshot of "Billing & Settings" for *working *app: 
> http://snag.gy/3RrJL.jpg
>
> In the last screenshot you can see that I'm missing a crucial part of the 
> page for some reason, for the project "st-app".
>
> Thank you!
>
>
>
> Den fredag 20 mars 2015 kl. 17:05:09 UTC+1 skrev Dan Stokeley:
>>
>> Hi Rasmus,
>>
>> You can set the Daily Budget in the Developers Console. Visit 
>> https://console.developers.google.com/project/st-app/appengine/settings 
>> and you can change it there.
>>
>> Regards,
>>
>> Dan Stokeley
>> Cloud Billing Product Manager
>>
>> On Friday, 20 March 2015 03:00:28 UTC-7, Rasmus Vernhamn wrote:
>>>
>>> I've created an App Engine project (Project ID: st-app). I enabled 
>>> billing through the Cloud Console, using an existing billing account. But 
>>> the changes (enabling of billing) isn't propogated to the App Engine 
>>> project. Meaning, in App Engine (old dashboard) I can't set the Daily 
>>> Budget and the "Enable Billing"-button is disabled.
>>>
>>> Thank you!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/664ecee5-6a0a-4d01-ab91-2a0556f31cae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cloud Billing is enabled but isn't propogated to App Engine project

[Dan Stokeley]

Hi Rasmus,

You can set the Daily Budget in the Developers Console. 
Visit https://console.developers.google.com/project/st-app/appengine/settings 
and you can change it there.

Regards,

Dan Stokeley
Cloud Billing Product Manager

On Friday, 20 March 2015 03:00:28 UTC-7, Rasmus Vernhamn wrote:
>
> I've created an App Engine project (Project ID: st-app). I enabled billing 
> through the Cloud Console, using an existing billing account. But the 
> changes (enabling of billing) isn't propogated to the App Engine project. 
> Meaning, in App Engine (old dashboard) I can't set the Daily Budget and the 
> "Enable Billing"-button is disabled.
>
> Thank you!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/209ca060-d020-4c20-acb1-f140fc9094ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] HTTP/2 Protocol Support

[Dan Dubois]

Does App Engine support the HTTP/2 protocol?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/35be25e4-091a-4091-9207-f840958cda27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] How should I avoid this 500 Server Internal Error when trying to pull google/appengine-java image for Managed VMs?

['Dan Lorenc' via Google App Engine]

Hey,

Sorry for the slow response. From your logs, it looks like everything was
working fine until a network-related error happened. Have you tried
retrying?

I haven't been able to repro this. If it keeps happening, could you also
add the output of "boot2docker version" and "gcloud version"? That will
help me get the exact versions you're using.

Dan Lorenc

On Sat Dec 27 2014 at 3:34:47 AM Nick  wrote:

> Hi Dan,
> Still getting the "Image not found error here"
>
> I updated boot2docker to v1.4.1 and gcloud to v9.0.41, but it's still the
> same.
> I pasted all the three logs you requested on pastebin
> Output of: gcloud --verbosity=debug preview app setup-managed-vms
> <http://pastebin.com/S45JqUV2>
> Output of: docker ps -a <http://pastebin.com/Aqi9nJmH>
> Logs from the registry container <http://pastebin.com/ZGdw09fN>
>
> Let me know if you have the same problems you had with boot2docker v1.3.1
> and want me to post a log from some other version.
>
> On Wednesday, December 17, 2014 8:06:10 PM UTC+1, Dan Lorenc wrote:
>
>> Hey,
>>
>> You should definitely be able to run setup-managed-vms and run your all
>> locally without triggering the free trial.
>>
>> Dan Lorenc
>>
>
>>
>> On Mon Dec 15 2014 at 8:56:47 AM Nick  wrote:
>>
>>> I just wanted to add, I have not enabled compute engine billing in my
>>> account. I would like to test my app locally first, before to deploy it to
>>> Managed VMs not to waste the 60 days of free trial.
>>> This shouldn't be an issue with the `gcloud preview app
>>> setup-managed-vms`command, right?
>>>
>>> If it is, how can I run a Managed VMs app locally, without wasting the
>>> trial?
>>>
>>>
>>> On Monday, December 15, 2014 6:56:25 AM UTC+1, Dan Lorenc wrote:
>>>
>>>> Can you attach the logs from the registry container?
>>>>
>>>> From the logs you posted, the command would be:
>>>> docker logs e8cd6049560a
>>>>
>>>> Dan Lorenc
>>>>
>>>> On Sun Dec 14 2014 at 9:46:13 PM Saleem Ansari 
>>>> wrote:
>>>>
>>> Hi Dan,
>>>>>
>>>>> Please find my replies below.
>>>>>
>>>>>
>>>>> > Sorry for the confusion.
>>>>> > I think the answer in that stack overflow post is actually
>>>>> incorrect, and causing the current problem you're seeing. To fix it you'll
>>>>> need to remove the google/docker-registry image. The easiest way is to
>>>>> boot2docker delete, boot2docker init, boot2docker up. Then you can run
>>>>> setup-managed-vms again.
>>>>>
>>>>> I followed the steps you mentioned, still I am facing issues. Details
>>>>> are posted here : https://gist.github.com/xuru/6
>>>>> 04da3c02ec96904d352#comment-1356364
>>>>>
>>>>> Here is the summary
>>>>>
>>>>> * Created image with Boot2Docker version 1.3.3
>>>>> * Update to Google SDK 0.9.40
>>>>> * gcloud init
>>>>> * gcloud --verbosity=debug preview app setup-managed-vms
>>>>>
>>>>> I get this error from gcloud tool
>>>>>
>>>>> google.appengine.tools.docker.containers.ImageError: Image with tag
>>>>> localhost:49154/google/appengine-python27 was not found
>>>>>
>>>>>
>>>>> Docker daemon log shows this:
>>>>>
>>>>> [debug] endpoint.go:59 Error from registry "
>>>>> https://localhost:49154/v1/"; marked as insecure: Get
>>>>> https://localhost:49154/v1/_ping: read tcp 127.0.0.1:49154:
>>>>> connection reset by peer. Insecurely falling back to HTTP Invalid registry
>>>>> endpoint "http://localhost:49154/v1/";. HTTPS attempt: Get
>>>>> https://localhost:49154/v1/_ping: read tcp 127.0.0.1:49154:
>>>>> connection reset by peer. HTTP attempt: Get
>>>>> http://localhost:49154/v1/_ping: read tcp 127.0.0.1: 49154:
>>>>> connection reset by peer
>>>>>
>>>>> Regards,
>>>>> Saleem
>>>>>
>>>>>
>>>>>
>>>>>  --
>>>>> 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 htt

Re: [google-appengine] How should I avoid this 500 Server Internal Error when trying to pull google/appengine-java image for Managed VMs?

['Dan Lorenc' via Google App Engine]

Hey,

You should definitely be able to run setup-managed-vms and run your all
locally without triggering the free trial.

Dan Lorenc

On Mon Dec 15 2014 at 8:56:47 AM Nick  wrote:

> I just wanted to add, I have not enabled compute engine billing in my
> account. I would like to test my app locally first, before to deploy it to
> Managed VMs not to waste the 60 days of free trial.
> This shouldn't be an issue with the `gcloud preview app
> setup-managed-vms`command, right?
>
> If it is, how can I run a Managed VMs app locally, without wasting the
> trial?
>
>
> On Monday, December 15, 2014 6:56:25 AM UTC+1, Dan Lorenc wrote:
>
>> Can you attach the logs from the registry container?
>>
>> From the logs you posted, the command would be:
>> docker logs e8cd6049560a
>>
>> Dan Lorenc
>>
>> On Sun Dec 14 2014 at 9:46:13 PM Saleem Ansari  wrote:
>>
> Hi Dan,
>>>
>>> Please find my replies below.
>>>
>>>
>>> > Sorry for the confusion.
>>> > I think the answer in that stack overflow post is actually incorrect,
>>> and causing the current problem you're seeing. To fix it you'll need to
>>> remove the google/docker-registry image. The easiest way is to boot2docker
>>> delete, boot2docker init, boot2docker up. Then you can run
>>> setup-managed-vms again.
>>>
>>> I followed the steps you mentioned, still I am facing issues. Details
>>> are posted here : https://gist.github.com/xuru/
>>> 604da3c02ec96904d352#comment-1356364
>>>
>>> Here is the summary
>>>
>>> * Created image with Boot2Docker version 1.3.3
>>> * Update to Google SDK 0.9.40
>>> * gcloud init
>>> * gcloud --verbosity=debug preview app setup-managed-vms
>>>
>>> I get this error from gcloud tool
>>>
>>> google.appengine.tools.docker.containers.ImageError: Image with tag
>>> localhost:49154/google/appengine-python27 was not found
>>>
>>>
>>> Docker daemon log shows this:
>>>
>>> [debug] endpoint.go:59 Error from registry "https://localhost:49154/v1/";
>>> marked as insecure: Get https://localhost:49154/v1/_ping: read tcp
>>> 127.0.0.1:49154: connection reset by peer. Insecurely falling back to
>>> HTTP Invalid registry endpoint "http://localhost:49154/v1/";. HTTPS
>>> attempt: Get https://localhost:49154/v1/_ping: read tcp 127.0.0.1:49154:
>>> connection reset by peer. HTTP attempt: Get http://localhost:49154/v1/_
>>> ping: read tcp 127.0.0.1: 49154: connection reset by peer
>>>
>>> Regards,
>>> Saleem
>>>
>>>
>>>
>>>  --
>>> 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/UFRalrQtMAs/unsubscribe.
>>>
>> To unsubscribe from this group and all its topics, send an email to
>>> google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>
>>
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
> 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/UFRalrQtMAs/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] How should I avoid this 500 Server Internal Error when trying to pull google/appengine-java image for Managed VMs?

['Dan Lorenc' via Google App Engine]

Can you attach the logs from the registry container?

>From the logs you posted, the command would be:
docker logs e8cd6049560a

Dan Lorenc

On Sun Dec 14 2014 at 9:46:13 PM Saleem Ansari  wrote:

> Hi Dan,
>
> Please find my replies below.
>
>
> > Sorry for the confusion.
> > I think the answer in that stack overflow post is actually incorrect,
> and causing the current problem you're seeing. To fix it you'll need to
> remove the google/docker-registry image. The easiest way is to boot2docker
> delete, boot2docker init, boot2docker up. Then you can run
> setup-managed-vms again.
>
> I followed the steps you mentioned, still I am facing issues. Details are
> posted here :
> https://gist.github.com/xuru/604da3c02ec96904d352#comment-1356364
>
> Here is the summary
>
> * Created image with Boot2Docker version 1.3.3
> * Update to Google SDK 0.9.40
> * gcloud init
> * gcloud --verbosity=debug preview app setup-managed-vms
>
> I get this error from gcloud tool
>
> google.appengine.tools.docker.containers.ImageError: Image with tag
> localhost:49154/google/appengine-python27 was not found
>
>
> Docker daemon log shows this:
>
> [debug] endpoint.go:59 Error from registry "https://localhost:49154/v1/";
> marked as insecure: Get https://localhost:49154/v1/_ping: read tcp
> 127.0.0.1:49154: connection reset by peer. Insecurely falling back to
> HTTP Invalid registry endpoint "http://localhost:49154/v1/";. HTTPS
> attempt: Get https://localhost:49154/v1/_ping: read tcp 127.0.0.1:49154:
> connection reset by peer. HTTP attempt: Get
> http://localhost:49154/v1/_ping: read tcp 127.0.0.1: 49154: connection
> reset by peer
>
> Regards,
> Saleem
>
>
>
>  --
> 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/UFRalrQtMAs/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] How should I avoid this 500 Server Internal Error when trying to pull google/appengine-java image for Managed VMs?

['Dan Lorenc' via Google App Engine]

Hey Everyone,

There are a couple unrelated problems that are getting confused together.
Some versions of boot2docker do not work with the gcloud SDK, and the
public google/docker-registry docker image also does not work with the
gcloud SDK. Please give this set of steps a try:

boot2docker delete
boot2docker download --iso-url=
https://github.com/boot2docker/boot2docker/releases/download/v1.3.3/boot2docker.iso
boot2docker init
boot2docker up

gcloud components update app
gcloud preview app setup-managed-vms

If you're still hitting trouble:

Make sure the version of docker in the boot2docker VM is 1.3.0, 1.3.2 or
1.3.3. To do this, run:
boot2docker ssh
docker version
The 'Server Version' field should be 1.3.0,1.3.2 or 1.3.3.

Make sure gcloud is up to date, run:
gcloud version
This should say: "Google Cloud SDK 0.9.40"

Finally, make sure you're logged into gcloud correctly. Run:
gcloud auth login

If you have the correct versions above, some log files will be very
helpful. Please attach:
The output of:
gcloud --verbosity=debug preview app setup-managed-vms

The logs from the docker-registry container. You can get these by running:
docker ps -a

Then look in the output for the most recent container with the Image named
"google/docker-registry:latest". Copy the Container ID field, and run:
docker logs 

Thanks,
Dan Lorenc



On Sun Dec 14 2014 at 1:37:02 PM Saleem Ansari  wrote:

>
>
> On Saturday, December 13, 2014 4:03:36 PM UTC+5:30, Nick wrote:
>>
>> Trying with Google Cloud SDK v0.9.40 now. Fails with this error
>>
>> google.appengine.tools.docker.containers.ImageError: Image with tag
>> localhost:49153/google/appengine-java was not found
>>
>>
> I am using gcloud v0.9.40 and I am also facing issues:
>
> https://gist.github.com/xuru/604da3c02ec96904d352#comment-1355911
>
> I think these are related.
>
> Regards,
> Saleem
>
>
>
>  --
> 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/UFRalrQtMAs/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] How should I avoid this 500 Server Internal Error when trying to pull google/appengine-java image for Managed VMs?

[Dan Lorenc]

Hey,

Sorry for the confusion.

I think the answer in that stack overflow post is actually incorrect, and 
causing the current problem you're seeing. To fix it you'll need to remove 
the google/docker-registry image. The easiest way is to boot2docker delete, 
boot2docker init, boot2docker up. Then you can run setup-managed-vms again.

Dan Lorenc

On Saturday, December 13, 2014 2:33:36 AM UTC-8, Nick wrote:
>
> Trying with Google Cloud SDK v0.9.40 now. Fails with this error 
>
> google.appengine.tools.docker.containers.ImageError: Image with tag 
> localhost:49153/google/appengine-java was not found
>
> On Wednesday, December 10, 2014 7:23:57 AM UTC+1, Vinny P wrote:
>>
>> On Tue, Dec 9, 2014 at 9:36 AM, Nick  wrote:
>>
>>> *This is the stacktrace, with the verbosity set to debug level:*
>>>
>>> googlecloudsdk.appengine.lib.images.util.DockerPullError: Error pulling 
>>> google/appengine-java: 500 Server Error: Internal Server Error ("Invalid 
>>> Registry endpoint: Get http://localhost:49157/v1/_ping: read tcp 
>>> 127.0.0.1:49157: connection reset by peer")
>>>
>>
>>
>> Can you try again, but this time use the insecure registry option: 
>> http://stackoverflow.com/a/26832581 ?
>>
>> Before you try that though, can you check if your boot2docker VM has 
>> network access? Run a curl request on a website or another similar 
>> application to check.
>>  
>>  
>> -
>> -Vinny P
>> Technology & Media Consultant
>> Chicago, IL
>>
>> App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Why are cloud endpoints so slow ?

[Dan Ciruli]

>
> On Sat, Nov 15, 2014 at 8:28 AM, J Jones  > wrote:
>
>> Not sure if Google Endpoints are serious or not.  My appengine instance 
>> is warm and serving http request very quickly.  However, my endpoints are 
>> ranging from 3 seconds to 9 seconds... the endpoint just returns a 
>> hardcoded object so there's 0 happening there.  What a joke.
>>
>>
> J Jones -

Please see some notes from earlier in the thread. With our current 
architecture, "warming up" means not just warming up your AppEngine back 
end but (possibly numerous) API proxy. It may take up to 50 RPCs to ensure 
that your API is "warm" in proxy layer (across all instances). Try running 
a quick for loop to see if this improves the performance.

And: yes, we are working on an improvement to this warmup behavior. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Billing + Renewed Credit Card = Cancer

[Dan Stokeley]

Hi Kaan,

To update the credit card with a different expiry date, please follow the 
"Update a form of payment" instructions 
here: https://support.google.com/cloudbilling/answer/4356091 .

Even if the CVV has changed, you only need to update the expiry date for 
the card.

Regards

Dan Stokeley
Cloud Billing PM

On Wednesday, 3 September 2014 12:56:11 UTC-7, Kaan Soral wrote:
>
> Thanks for the replies
>
> No I haven't created an issue, they said the issue tracker would be more 
> active, but I've yet to see a change
>
> I'm outside US, so direct bank deposits, for N(~5) apps, would be death
>
> Your experience is very interesting Doug, I guess in US they have that 
> level of integration, I'm guessing it's the reason why I'm experiencing 
> this, since they have that capability in US, I'm guessing they didn't give 
> much thought into manual replacement
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Datastore eventual consistency

[Dan]

Thanks for the answer.

The results I am seeing are not because of ndb caching as it does not cache 
queries by property.

I imagine that the datastore eventual consistency has always been fast 
enough so the required indexes are updated by the time I run a put, then 
get operation making the subsequent query by property always work so far in 
testing. Thanks for making it clear that there is no technical 
reason/guarantee to rely on this.

On Sunday, July 20, 2014 11:36:49 PM UTC+1, Jeff Schnitzer wrote:
>
> The answer to your question is no.
>
> Queries are eventually consistent because index changes are replicated 
> between datacenters asynchronously and queries are served by any 
> datacenter. Strongly consistent get-by-key operations require a quorum of 
> datacenters; they have no effect on query index replication.
>
> Note that while get-by-key is strongly consistent by default, you can 
> explicitly request an eventually consistent get-by-key. Since it returns 
> the first result as-is (without waiting for a quorum), it is quite a bit 
> faster.
>
> Also: You may be experiencing cache behavior; ndb caches at both session 
> and memcache level.
>
> Jeff
>
>
> On Fri, Jul 18, 2014 at 2:17 PM, Dan > 
> wrote:
>
>> Apologies Chad, I didn't make myself clear. I was using Python ndb 
>> terminology with 'get', 'put' and 'query'.
>>
>> What I want to clarify is if an entity will always be returned from a 
>> fetch by kind if it has previously been fetched by key.
>>
>> This is what I experience in testing. I also remember reading that an 
>> entity's indexed properties are written to their respective indexes, if not 
>> done already, on its first fetch by key.
>>
>> Therefore can you effectively get strong consistency by adding a fetch by 
>> key after adding an entity to the datastore?
>>
>> Example 1:
>> 1) Put entity A.
>> 2) Query for entity A by kind. // This does not always return entity A 
>> due to the eventual consistency nature of the datastore.
>>
>> Example 2:
>> 1) Put entity B.
>> 2) Fetch entity B by key.
>> 3) Query for entity B by kind. // Always appears to return entity B.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore eventual consistency

[Dan]

Apologies Chad, I didn't make myself clear. I was using Python ndb terminology 
with 'get', 'put' and 'query'.

What I want to clarify is if an entity will always be returned from a fetch by 
kind if it has previously been fetched by key.

This is what I experience in testing. I also remember reading that an entity's 
indexed properties are written to their respective indexes, if not done 
already, on its first fetch by key.

Therefore can you effectively get strong consistency by adding a fetch by key 
after adding an entity to the datastore?

Example 1:
1) Put entity A.
2) Query for entity A by kind. // This does not always return entity A due to 
the eventual consistency nature of the datastore.

Example 2:
1) Put entity B.
2) Fetch entity B by key.
3) Query for entity B by kind. // Always appears to return entity B.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Datastore eventual consistency

[Dan]

Eventual consistency means that it will take a undetermined amount of time 
after a datastore entity 'put' for a query on that entity to be returned.

However am I right in thinking that if I 'put' the entity then 'get' it 
straight away then a subsequent query will ALWAYS return it?

This behaviour seems to be the case in the dev app server and in production but 
I would like confirmation that this is guaranteed to happen.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: gae billing vs. cloud billing

[Dan Stokeley]

Hi James,

Yes, we are planning to move billing for existing applications that are 
currently billed through the App Engine admin console to the Developers 
Console. This should happen in the coming weeks.

If an app has billing set up both in the App Engine admin console and for 
other cloud services in the project (what you referred to as cloud billing) 
we will begin billing these solely through the billing account of the 
project. This will allow you to manage billing for both the application and 
the other cloud services in the project in a single billing account in the 
Developers 
Console <https://console.developers.google.com/billing>. We will notify 
affected developers when we make this change, in the next few weeks. After 
the change has been made, you will still be able to access the original 
billing history of the App Engine application via the billing tab in the 
Developers Console.

You should verify that your billing details are up to date in the Developers 
Console <https://console.developers.google.com/billing>. If you need to 
update your form of payment on any billing account, please follow the 
instructions 
here <https://support.google.com/cloudbilling/answer/4356091>.

Regards,

Dan Stokeley
Cloud Platform Billing Product Manager

On Friday, 6 June 2014 08:25:15 UTC-7, James Gilliam wrote:
>
> For new appid's we are required to use cloud billing and old appids are 
> using gae billing -- confusing?  yes
>
> Will the old billing be moved to cloud billing or is this something we can 
> do to make this happen?
>
> Also, what happens if an appid has both gae billing and cloud billing for 
> other cloud services?
>
> Any help would be appreciated.
>
> 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

I should add that I guess this also means you don't need a Google Apps 
account for custom domains anymore! Another thing we have all been waiting 
for.

On Friday, April 11, 2014 8:54:24 PM UTC+1, Dan wrote:
>
> Amazing! It works! You can now serve naked domains with App Engine! 
>
> Barry, you are correct I did have my naked domain mapped to www in Google 
> Apps. However I removed the mapping prior to trying the new Google Console 
> Custom Domain Settings. I just assumed Google did something stupid like by 
> default redirect naked domains to www.
>
> In the end what I needed to do was completely disassociate my App Engine 
> app and my Google Apps account. Once I did this it all started to work. 
> Hooray, this is a feature we have all been waiting for since 2009! Thanks 
> Google I really appreciate the return of naked domain serving.
>
> On Friday, April 11, 2014 5:16:36 PM UTC+1, barryhunter wrote:
>>
>>
>>
>>
>> On 11 April 2014 16:56, Dan  wrote:
>>
>>> I raised this issue because I saw Google released their Cloud DNS 
>>> service and CloudFlare released there CNAME flattening service.
>>>
>>> I was also VERY hopeful about the new Google Console App Engine domain 
>>> mapping feature. Unfortunately, for me, it just redirects naked domains to 
>>> subdomains which is not what I want.
>>>
>>
>> Are you sure about that?
>>
>> When I looked at the control panel, you can set a mapping from the naken 
>> domain to Appengine. 
>>
>> For a redirect to work, it would have to tell you to setup the DNS for 
>> the naked domain, AND the DNS for whatever subdomain it redirects to. 
>>
>>
>>
>> In fact I just tried it, with a spare domain I had already verified with 
>> Google. I added it in the cloud control panel, then did a request
>>
>> # GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS
>>
>> ... I get the content from a AppEngine App (geodatastore). 
>>
>> No Redirect, no where else have setup a mapping from this domain to 
>> appengine. Note however also this mapping doesnt exist in DNS either (I'm 
>> just using it for testing purposes. . )
>>
>>
>> Maybe you are getting the redirect, because you have previouslly set it 
>> up in the Google Apps control panel? So its still managing the redirect, if 
>> so need to delete that so that the new cloud control panel can configure 
>> what happens with the domain. 
>>
>>
>>
>>  
>>
>>>  
>>> Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
>>> Plan will also not work with GAE naked domains.
>>>
>>> I guess I am stuck as I really don't want to run a reverse proxy on a 
>>> VPS somewhere.
>>>
>>> On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>>>
>>>>
>>>>
>>>>
>>>> On 11 April 2014 16:36, husayt  wrote:
>>>>
>>>>> This new google cloud DNS , might be interesting:
>>>>> https://developers.google.com/cloud-dns/
>>>>> but I have not looked into it.
>>>>>
>>>>
>>>> It doesnt help directly. It doesnt support ALIAS records nor particular 
>>>> intergration with AppEngine. 
>>>>
>>>>
>>>> ... it it offers no additional features beyond what would get at any 
>>>> other DNS provider. Its just useful if want to handle everything via 
>>>> Google. 
>>>>
>>>>
>>>> The new domain mapping feature just found, does indeed look like it 
>>>> will sort it :) Could use it with couldflare, with cloud-dns, or what ever 
>>>> dns provider you want. 
>>>>  
>>>>  
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

Amazing! It works! You can now serve naked domains with App Engine! 

Barry, you are correct I did have my naked domain mapped to www in Google 
Apps. However I removed the mapping prior to trying the new Google Console 
Custom Domain Settings. I just assumed Google did something stupid like by 
default redirect naked domains to www.

In the end what I needed to do was completely disassociate my App Engine 
app and my Google Apps account. Once I did this it all started to work. 
Hooray, this is a feature we have all been waiting for since 2009! Thanks 
Google I really appreciate the return of naked domain serving.

On Friday, April 11, 2014 5:16:36 PM UTC+1, barryhunter wrote:
>
>
>
>
> On 11 April 2014 16:56, Dan > wrote:
>
>> I raised this issue because I saw Google released their Cloud DNS service 
>> and CloudFlare released there CNAME flattening service.
>>
>> I was also VERY hopeful about the new Google Console App Engine domain 
>> mapping feature. Unfortunately, for me, it just redirects naked domains to 
>> subdomains which is not what I want.
>>
>
> Are you sure about that?
>
> When I looked at the control panel, you can set a mapping from the naken 
> domain to Appengine. 
>
> For a redirect to work, it would have to tell you to setup the DNS for the 
> naked domain, AND the DNS for whatever subdomain it redirects to. 
>
>
>
> In fact I just tried it, with a spare domain I had already verified with 
> Google. I added it in the cloud control panel, then did a request
>
> # GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS
>
> ... I get the content from a AppEngine App (geodatastore). 
>
> No Redirect, no where else have setup a mapping from this domain to 
> appengine. Note however also this mapping doesnt exist in DNS either (I'm 
> just using it for testing purposes. . )
>
>
> Maybe you are getting the redirect, because you have previouslly set it up 
> in the Google Apps control panel? So its still managing the redirect, if so 
> need to delete that so that the new cloud control panel can configure what 
> happens with the domain. 
>
>
>
>  
>
>>  
>> Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
>> Plan will also not work with GAE naked domains.
>>
>> I guess I am stuck as I really don't want to run a reverse proxy on a VPS 
>> somewhere.
>>
>> On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>>
>>>
>>>
>>>
>>> On 11 April 2014 16:36, husayt  wrote:
>>>
>>>> This new google cloud DNS , might be interesting:
>>>> https://developers.google.com/cloud-dns/
>>>> but I have not looked into it.
>>>>
>>>
>>> It doesnt help directly. It doesnt support ALIAS records nor particular 
>>> intergration with AppEngine. 
>>>
>>>
>>> ... it it offers no additional features beyond what would get at any 
>>> other DNS provider. Its just useful if want to handle everything via 
>>> Google. 
>>>
>>>
>>> The new domain mapping feature just found, does indeed look like it will 
>>> sort it :) Could use it with couldflare, with cloud-dns, or what ever dns 
>>> provider you want. 
>>>  
>>>  
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

I raised this issue because I saw Google released their Cloud DNS service 
and CloudFlare released there CNAME flattening service.

I was also VERY hopeful about the new Google Console App Engine domain 
mapping feature. Unfortunately, for me, it just redirects naked domains to 
subdomains which is not what I want.

Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
Plan will also not work with GAE naked domains.

I guess I am stuck as I really don't want to run a reverse proxy on a VPS 
somewhere.

On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>
>
>
>
> On 11 April 2014 16:36, husayt > wrote:
>
>> This new google cloud DNS , might be interesting:
>> https://developers.google.com/cloud-dns/
>> but I have not looked into it.
>>
>
> It doesnt help directly. It doesnt support ALIAS records nor particular 
> intergration with AppEngine. 
>
>
> ... it it offers no additional features beyond what would get at any other 
> DNS provider. Its just useful if want to handle everything via Google. 
>
>
> The new domain mapping feature just found, does indeed look like it will 
> sort it :) Could use it with couldflare, with cloud-dns, or what ever dns 
> provider you want. 
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

The new Custom Domains settings page in Google Console does just map 
redirect naked domains to subdomains as with previous functionality. :-(

On Friday, April 11, 2014 10:59:24 AM UTC+1, Dan wrote:
>
> Thanks for all the information. I especially like the blog post by Jeff. I 
> also found this on 
> StackOverflow<http://stackoverflow.com/questions/17612627/naked-domain-redirect-failing-when-using-https-ssl-on-google-app-engine>
>  which 
> seems useful.
>
> Having said all that, I raised this question of naked domains again on 
> StackOverflow 
> and someone pointed 
> out<http://stackoverflow.com/questions/22993969/how-do-i-use-a-naked-apex-domain-with-app-engine>that
>  there is a new settings page at 
> https://console.developers.google.com/project that allows you to link 
> naked domains to App Engine! I am trying it out now and will report back. I 
> bet it just redirects naked http domains like the original functionality 
> though.
>
> On Thursday, April 10, 2014 11:39:20 PM UTC+1, Jeff Schnitzer wrote:
>>
>> Unless CF provides some way of rewriting the Host: header, it won't 
>> work because ultimately Google will reject the naked domain request. A 
>> long time ago CF actually provided this ability, but then they removed 
>> it for reasons I do not understand. You can always ask to bring it 
>> back. 
>>
>> We use CF for SSL (see 
>> http://blorn.com/post/20185054195/ssl-for-your-domain-on-google-app-engine<http://www.google.com/url?q=http%3A%2F%2Fblorn.com%2Fpost%2F20185054195%2Fssl-for-your-domain-on-google-app-engine&sa=D&sntz=1&usg=AFQjCNHKkwC1mJzNgcgkgHwlIcJXsK12sw>),
>>  
>>
>> but we wouldn't try this trick with naked domains even if it worked - 
>> you'd be permanently dependent on CF. I like being able to yank them 
>> out of the pipeline if necessary. 
>>
>> Jeff 
>>
>>
>> On Thu, Apr 10, 2014 at 2:44 PM, PK  wrote: 
>> > I have read in this list that others have gotten this to work. However, 
>> I 
>> > have not pursued it because the state of the art of this integration 
>> means 
>> > that traffic from CloudFlare Data Center(s) to Google Data Center(s) 
>> will be 
>> > unencrypted and this does not pass my end to end security standards. 
>> > 
>> > PK 
>> > http://www.gae123.com 
>> > 
>> > On April 10, 2014 at 12:31:53 PM, Dan (uvic...@gmail.com) wrote: 
>> > 
>> > Thanks for the info. Interesting that naked domains may work with 
>> > CloudFlare's Flexible SSL option. 
>> > 
>> > Can anyone confirm this? I don't want to spend $20 for their pro plan 
>> just 
>> > to find out it does not work. CloudFlare's support has not been that 
>> great. 
>> > The support guy still thinks it should all just work even without SSL 
>> turned 
>> > on and advised me to 'check my settings on GAE'... 
>> > 
>> > On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote: 
>> >> 
>> >> 
>> >> 
>> >>> 
>> >>> I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
>> but 
>> >>> with no success. 
>> >> 
>> >> 
>> >> That doesnt work on its own, because CloudFlare's proxy will send the 
>> HTTP 
>> >> Host header, still set to mydomain.com back to the origin (AppEngine) 
>> - in 
>> >> that situation, AppEngine has no way of knowing what appid, is meant 
>> to 
>> >> serve the domain. 
>> >> 
>> >> 
>> >> 
>> >> 
>> >>> 
>> >>> 
>> >>> If you have made naked domains work with GAE, how did you do it? 
>> >> 
>> >> 
>> >> You need a proxy, capable of rewriting the http host header. There are 
>> >> commerical services that offer this. 
>> >> 
>> >> I've done it previously using Varnish on a small VPS. quite easy to 
>> setup 
>> >> if have some basic linux knowledge. 
>> >> 
>> >> 
>> >> And I do know edgecast CDN does offer http header rewriting, but not 
>> tried 
>> >> it with AppEngine. 
>> >> 
>> >> 
>> >> People using CloudFlare with AppEngine, I think is using the SSL 
>> option, 
>> >> where the Flexible SSL option may well offer host header rewriting 
>> (because 
>> >> it reterminates SSL) - so using the SSL option, even if you dont 
>

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

Thanks for all the information. I especially like the blog post by Jeff. I 
also found this on 
StackOverflow<http://stackoverflow.com/questions/17612627/naked-domain-redirect-failing-when-using-https-ssl-on-google-app-engine>
 which 
seems useful.

Having said all that, I raised this question of naked domains again on 
StackOverflow 
and someone pointed 
out<http://stackoverflow.com/questions/22993969/how-do-i-use-a-naked-apex-domain-with-app-engine>that
 there is a new settings page at 
https://console.developers.google.com/project that allows you to link naked 
domains to App Engine! I am trying it out now and will report back. I bet 
it just redirects naked http domains like the original functionality though.

On Thursday, April 10, 2014 11:39:20 PM UTC+1, Jeff Schnitzer wrote:
>
> Unless CF provides some way of rewriting the Host: header, it won't 
> work because ultimately Google will reject the naked domain request. A 
> long time ago CF actually provided this ability, but then they removed 
> it for reasons I do not understand. You can always ask to bring it 
> back. 
>
> We use CF for SSL (see 
> http://blorn.com/post/20185054195/ssl-for-your-domain-on-google-app-engine<http://www.google.com/url?q=http%3A%2F%2Fblorn.com%2Fpost%2F20185054195%2Fssl-for-your-domain-on-google-app-engine&sa=D&sntz=1&usg=AFQjCNHKkwC1mJzNgcgkgHwlIcJXsK12sw>),
>  
>
> but we wouldn't try this trick with naked domains even if it worked - 
> you'd be permanently dependent on CF. I like being able to yank them 
> out of the pipeline if necessary. 
>
> Jeff 
>
>
> On Thu, Apr 10, 2014 at 2:44 PM, PK > 
> wrote: 
> > I have read in this list that others have gotten this to work. However, 
> I 
> > have not pursued it because the state of the art of this integration 
> means 
> > that traffic from CloudFlare Data Center(s) to Google Data Center(s) 
> will be 
> > unencrypted and this does not pass my end to end security standards. 
> > 
> > PK 
> > http://www.gae123.com 
> > 
> > On April 10, 2014 at 12:31:53 PM, Dan (uvic...@gmail.com ) 
> wrote: 
> > 
> > Thanks for the info. Interesting that naked domains may work with 
> > CloudFlare's Flexible SSL option. 
> > 
> > Can anyone confirm this? I don't want to spend $20 for their pro plan 
> just 
> > to find out it does not work. CloudFlare's support has not been that 
> great. 
> > The support guy still thinks it should all just work even without SSL 
> turned 
> > on and advised me to 'check my settings on GAE'... 
> > 
> > On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote: 
> >> 
> >> 
> >> 
> >>> 
> >>> I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
> but 
> >>> with no success. 
> >> 
> >> 
> >> That doesnt work on its own, because CloudFlare's proxy will send the 
> HTTP 
> >> Host header, still set to mydomain.com back to the origin (AppEngine) 
> - in 
> >> that situation, AppEngine has no way of knowing what appid, is meant to 
> >> serve the domain. 
> >> 
> >> 
> >> 
> >> 
> >>> 
> >>> 
> >>> If you have made naked domains work with GAE, how did you do it? 
> >> 
> >> 
> >> You need a proxy, capable of rewriting the http host header. There are 
> >> commerical services that offer this. 
> >> 
> >> I've done it previously using Varnish on a small VPS. quite easy to 
> setup 
> >> if have some basic linux knowledge. 
> >> 
> >> 
> >> And I do know edgecast CDN does offer http header rewriting, but not 
> tried 
> >> it with AppEngine. 
> >> 
> >> 
> >> People using CloudFlare with AppEngine, I think is using the SSL 
> option, 
> >> where the Flexible SSL option may well offer host header rewriting 
> (because 
> >> it reterminates SSL) - so using the SSL option, even if you dont 
> strictly 
> >> need SSL, might work. 
> >> 
> >> 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Google App Engine" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to google-appengi...@googlegroups.com . 
> > To post to this group, send email to 
> > google-a...@googlegroups.com. 
>
> > Visit this group at http://groups.google.com/group/google-appengine. 
> > For more options, visit https://groups.google.com/d/optout. 

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

Thanks for the info. Interesting that naked domains may work with 
CloudFlare's Flexible SSL option.

Can anyone confirm this? I don't want to spend $20 for their pro plan just 
to find out it does not work. CloudFlare's support has not been that great. 
The support guy still thinks it should all just work even without SSL 
turned on and advised me to 'check my settings on GAE'...

On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote:
>
>
>  
>
>>  I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
>> but with no success.
>>
>
> That doesnt work on its own, because CloudFlare's proxy will send the HTTP 
> Host header, still set to mydomain.com back to the origin (AppEngine) - 
> in that situation, AppEngine has no way of knowing what appid, is meant to 
> serve the domain. 
>
>
>
>  
>
>>  
>> If you have made naked domains work with GAE, how did you do it?
>>
>
> You need a proxy, capable of rewriting the http host header. There are 
> commerical services that offer this. 
>
> I've done it previously using Varnish on a small VPS. quite easy to setup 
> if have some basic linux knowledge. 
>
>
> And I do know edgecast CDN does offer http header rewriting, but not tried 
> it with AppEngine. 
>  
>
> People using CloudFlare with AppEngine, I think is using the SSL option, 
> where the Flexible SSL option may well offer host header rewriting (because 
> it reterminates SSL) - so using the SSL option, even if you dont strictly 
> need SSL, might work. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] App Engine and naked/apex domains

[Dan]

I know this comes up all the time but can someone give me an example of how 
they have made their naked domain work with App Engine? I posted this 
questionon
 StackOverflow. Note that I don't want to redirect from mydomain.com to 
www.mydomain.com, I want to serve from mydomain.com.

Its clearly not possible to use Google Apps custom domains as they only 
work with sub domains. Therefore I thought a reverse proxy would work and I 
see some people mention CloudFlare. Seeing as they just released their 
CNAME flattening service specifically for naked domains I thought I might 
have some success. This doesn't seem to work either - I don't know why. I 
have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' but with 
no success.

If you have made naked domains work with GAE, how did you do 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Help Solving NameError: name 'guestbook_name' is not defined.

[Dan Sprague]

I figured it out...I used the cloud playground to examine the guestbook.py 
code and saw that my file had some additional code that needed to be 
removed. Everything is working as expected now.

On Wednesday, March 26, 2014 9:18:00 PM UTC-4, Dan Sprague wrote:
>
> Vinny,
>
> I am using the app.yaml with the libraries added, made the changes 
> MainPage handler changes to guestbook.py, and created the HTML index file 
> as outlined in the tutorial but, no luck. 
>
> Thanks for your help I appreciate the reply!
>
> On Wednesday, March 26, 2014 2:06:19 AM UTC-4, Vinny P wrote:
>>
>> On Mon, Mar 24, 2014 at 8:25 PM, Dan Sprague  wrote:
>>
>>> I am walking through the Google Application Engine Python tutorial for 
>>> building a guestbook and have it a snag. I am following the instrcutions in 
>>> the using templates section of the process and I can't seem to overcome 
>>> this simple name issue: NameError: name 'guestbook_name' is not defined. 
>>>
>>> Here is the error message from Google Application Launcher:
>>>
>>> File "/Users/spragued/Desktop/guestbook/guestbook.py", line 56, in 
>>> MainPage
>>>
>>> ancestor=guestbook_key(guestbook_name)).order(-Greeting.date)
>>>
>>> NameError: name 'guestbook_name' is not defined
>>>
>>> INFO 2014-03-24 00:05:36,343 module.py:621] default: "GET 
>>> /?guestbook_name=default_guestbook HTTP/1.1" 500 -
>>>
>>>  
>>
>> Is your application loading in the template files that are part of the 
>> tutorial? The template files are important because they assign the value of 
>> *guestbook_name*. Make sure you've added in all the files listed in 
>> https://developers.google.com/appengine/docs/python/gettingstartedpython27/templates.
>>
>>  
>>  
>> -
>> -Vinny P
>> Technology & Media Advisor
>> Chicago, IL
>>
>> App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Help Solving NameError: name 'guestbook_name' is not defined.

[Dan Sprague]

Vinny,

I am using the app.yaml with the libraries added, made the changes MainPage 
handler changes to guestbook.py, and created the HTML index file as 
outlined in the tutorial but, no luck. 

Thanks for your help I appreciate the reply!

On Wednesday, March 26, 2014 2:06:19 AM UTC-4, Vinny P wrote:
>
> On Mon, Mar 24, 2014 at 8:25 PM, Dan Sprague 
> > wrote:
>
>> I am walking through the Google Application Engine Python tutorial for 
>> building a guestbook and have it a snag. I am following the instrcutions in 
>> the using templates section of the process and I can't seem to overcome 
>> this simple name issue: NameError: name 'guestbook_name' is not defined. 
>>
>> Here is the error message from Google Application Launcher:
>>
>> File "/Users/spragued/Desktop/guestbook/guestbook.py", line 56, in 
>> MainPage
>>
>> ancestor=guestbook_key(guestbook_name)).order(-Greeting.date)
>>
>> NameError: name 'guestbook_name' is not defined
>>
>> INFO 2014-03-24 00:05:36,343 module.py:621] default: "GET 
>> /?guestbook_name=default_guestbook HTTP/1.1" 500 -
>>
>>  
>
> Is your application loading in the template files that are part of the 
> tutorial? The template files are important because they assign the value of 
> *guestbook_name*. Make sure you've added in all the files listed in 
> https://developers.google.com/appengine/docs/python/gettingstartedpython27/templates.
>
>  
>  
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

{% autoescape true %}

  
{% for greeting in greetings %}
  {% if greeting.author %}
{{ greeting.author.nickname() }} wrote:
  {% else %}
   An anonymous person wrote:
  {% endif %}
  {{ greeting.content }}
{% endfor %}


  
  




Guestbook name:
  
  


{{ url_linktext }}

  

{% endautoescape %}

app.yaml
Description: Binary data
import os
import urllib

from google.appengine.api import users
from google.appengine.ext import ndb

import jinja2
import webapp2

JINJA_ENVIRONMENT = jinja2.Environment(
loader=jinja2.FileSystemLoader(os.path.dirname(__file__)),
extensions=['jinja2.ext.autoescape'],
autoescape=True)

MAIN_PAGE_FOOTER_TEMPLATE = """\

  
  




Guestbook name:
  
  


%s

  

"""

DEFAULT_GUESTBOOK_NAME = 'default_guestbook'

# We set a parent key on the 'Greetings' to ensure that they are all in the same
# entity group. Queries across the single entity group will be consistent.
# However, the write rate should be limited to ~1/second.

def guestbook_key(guestbook_name=DEFAULT_GUESTBOOK_NAME):
"""Constructs a Datastore key for a Guestbook entity with guestbook_name."""
return ndb.Key('Guestbook', guestbook_name)

class Greeting(ndb.Model):
"""Models an individual Guestbook entry with author, content, and date."""
author = ndb.UserProperty()
content = ndb.StringProperty(indexed=False)
date = ndb.DateTimeProperty(auto_now_add=True)

class MainPage(webapp2.RequestHandler):

def get(self):
guestbook_name = self.request.get('guestbook_name',
  DEFAULT_GUESTBOOK_NAME)
greetings_query = Greeting.query(
ancestor=guestbook_key(guestbook_name)).order(-Greeting.date)
greetings = greetings_query.fetch(10)

if users.get_current_user():
url = users.create_logout_url(self.request.uri)
url_linktext = 'Logout'
else:
url = users.create_login_url(self.request.uri)
url_linktext = 'Login'

template_values = {
'greetings': greetings,
'guestbook_name': urllib.quote_plus(guestbook_name),
'url': url,
'url_linktext': url_linktext,
}

template = JINJA_ENVIRONMENT.get_template('index.html')
self.response.write(template.render(template_values))


class Guestbook(webapp2.RequestHandler):

def post(self):
# We set the same parent key

[google-appengine] Help Solving NameError: name 'guestbook_name' is not defined.

[Dan Sprague]

I am walking through the Google Application Engine Python tutorial for 
building a guestbook and have it a snag. I am following the instrcutions in 
the using templates section of the process and I can't seem to overcome 
this simple name issue: NameError: name 'guestbook_name' is not defined. 

Here is the error message from Google Application Launcher:

File "/Users/spragued/Desktop/guestbook/guestbook.py", line 56, in MainPage

ancestor=guestbook_key(guestbook_name)).order(-Greeting.date)

NameError: name 'guestbook_name' is not defined

INFO 2014-03-24 00:05:36,343 module.py:621] default: "GET 
/?guestbook_name=default_guestbook HTTP/1.1" 500 -


I have attached my guestbook.py file for review...any help would be 
appreciated! 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 http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.
import os
import urllib

from google.appengine.api import users
from google.appengine.ext import ndb

import jinja2
import webapp2

JINJA_ENVIRONMENT = jinja2.Environment(
loader=jinja2.FileSystemLoader(os.path.dirname(__file__)),
extensions=['jinja2.ext.autoescape'],
autoescape=True)

MAIN_PAGE_FOOTER_TEMPLATE = """\

  
  




Guestbook name:
  
  


%s

  

"""

DEFAULT_GUESTBOOK_NAME = 'default_guestbook'

# We set a parent key on the 'Greetings' to ensure that they are all in the same
# entity group. Queries across the single entity group will be consistent.
# However, the write rate should be limited to ~1/second.

def guestbook_key(guestbook_name=DEFAULT_GUESTBOOK_NAME):
"""Constructs a Datastore key for a Guestbook entity with guestbook_name."""
return ndb.Key('Guestbook', guestbook_name)

class Greeting(ndb.Model):
"""Models an individual Guestbook entry with author, content, and date."""
author = ndb.UserProperty()
content = ndb.StringProperty(indexed=False)
date = ndb.DateTimeProperty(auto_now_add=True)

class MainPage(webapp2.RequestHandler):

def get(self):
guestbook_name = self.request.get('guestbook_name',
  DEFAULT_GUESTBOOK_NAME)
greetings_query = Greeting.query(
ancestor=guestbook_key(guestbook_name)).order(-Greeting.date)
greetings = greetings_query.fetch(10)

if users.get_current_user():
url = users.create_logout_url(self.request.uri)
url_linktext = 'Logout'
else:
url = users.create_login_url(self.request.uri)
url_linktext = 'Login'

template_values = {
'greetings': greetings,
'guestbook_name': urllib.quote_plus(guestbook_name),
'url': url,
'url_linktext': url_linktext,
}

template = JINJA_ENVIRONMENT.get_template('index.html')
self.response.write(template.render(template_values))


class Guestbook(webapp2.RequestHandler):

def post(self):
# We set the same parent key on the 'Greeting' to ensure each Greeting
# is in the same entity group. Queries across the single entity group
# will be consistent. However, the write rate to a single entity group
# should be limited to ~1/second.
guestbook_name = self.request.get('guestbook_name',
  DEFAULT_GUESTBOOK_NAME)
greeting = Greeting(parent=guestbook_key(guestbook_name))

if users.get_current_user():
greeting.author = users.get_current_user()

greeting.content = self.request.get('content')
greeting.put()

query_params = {'guestbook_name': guestbook_name}
self.redirect('/?' + urllib.urlencode(query_params))


application = webapp2.WSGIApplication([
('/', MainPage),
('/sign', Guestbook),
], debug=True)

[google-appengine] Implementing OAuth 2.0 'application only authentication' on App Engine

[Dan]

I have an App Engine server that provides a REST API and would like to 
protect it with OAuth 2.0. Applications that use my REST API will be run on 
headless servers and not have any user input i.e. no web browser redirects 
for users to enter their username and password.

Twitter does more or less what I want with its Application Only 
Auth which 
uses the Client Credentials 
Grant approach 
of OAuth 2.0.

Does the App Engine OAuth 
service allow 
me to do this? If so how? (I find the documentation confusing and can't get 
a 2-legged approach to work in any case.) Otherwise where should I look for 
an alternative as I don't want to reinvent the wheel especially with 
security related parts of my app.

I would appreciate pointers to Go resources, but Python would also work for 
me.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Elevated error rate and new instance startup on Go runtime

[Dan]

The errors went away after adding more logging and reuploading my code. The 
logging didn't reveal anything but I guess it must be my code that caused 
the problems some how.

On Wednesday, December 11, 2013 7:59:01 PM UTC, Dan wrote:
>
> I'm currently experiencing an increased error rate of 1.6% of requests and 
> new instance startup on almost every request. I see the elevated error rate 
> has been going for over 12 hours. The errors are:
>
>> A problem was encountered with the process that handled this request, 
>> causing it to exit. This is likely to cause a new process to be used for the 
>> next request to your application. (Error code 121)
>>
>>
> Anyone else experiencing difficulties? 
> https://code.google.com/status/appengine/ says everything is good.
>
>
> <https://lh6.googleusercontent.com/-c7K_hV-Z9k8/UqjCxH_50DI/AC4/FjpR2y3mUyg/s1600/Screen+Shot+2013-12-11+at+19.51.46.png><https://lh6.googleusercontent.com/-AICktzqYvCg/UqjDathHtbI/ADA/QW2PSOTGhO0/s1600/Screen+Shot+2013-12-11+at+19.56.00.png>
> Dan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Elevated error rate and new instance startup on Go runtime

[Dan]

I'm currently experiencing an increased error rate of 1.6% of requests and 
new instance startup on almost every request. I see the elevated error rate 
has been going for over 12 hours. The errors are:

> A problem was encountered with the process that handled this request, causing 
> it to exit. This is likely to cause a new process to be used for the next 
> request to your application. (Error code 121)
>
>
Anyone else experiencing difficulties? 
https://code.google.com/status/appengine/ says everything is good.

<https://lh6.googleusercontent.com/-c7K_hV-Z9k8/UqjCxH_50DI/AC4/FjpR2y3mUyg/s1600/Screen+Shot+2013-12-11+at+19.51.46.png><https://lh6.googleusercontent.com/-AICktzqYvCg/UqjDathHtbI/ADA/QW2PSOTGhO0/s1600/Screen+Shot+2013-12-11+at+19.56.00.png>
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Go's runtime dynamic HTTP get latency worse than Python's?

[Dan]

When I look at https://code.google.com/status/appengine I see that Python's 
Dynamic HTTP Get Latency hovers around 10ms and is fairly stable. However 
Go's hovers around 20ms and is much more erratic. Looking back on previous 
days I see the situation is sometimes worse for Go.

I expected the Go runtime to be slightly better as it is touted as the most 
performant runtime in several Google YouTube presentations. I see that the 
Java runtime is actually faster than the Go runtime on the Fibonacci CPU 
test and both are approximately twice as fast as the Python runtime.

Why is the Python runtime so much faster at HTTP Gets when compared to the 
Go runtime?
How come the Java runtime is faster than the Go runtime at the CPU based 
Fibonacci test?
Are these both an artefact of the Go runtime being experimental and maybe 
using older slower test hardware?

I have been using the Go runtime assuming it was the fastest in all 
situations but it appears not to be fastest in anything. Having said that, 
the Go language is a pleasure to use and probably the fastest language for 
me to develop with even with the relative paucity of third party libraries. 
So ultimately the Go runtime is still definitely a win for me and I have 
saved money porting my CPU intensive app from Python to it.

Best wishes,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: NDB strategy for keeping caches in sync with the datastore

[Dan]

Great references. I had not seen them before and they explain a lot. I was 
puzzled by why _LOCK_TIME was so long at 32 seconds but now I know it is to 
cater for the maximum datastore retry length of 30 seconds plus a little 
bit extra.

It looks like Guido had a difficult time of it before memcache compare and 
swap was available in the Python runtime. Thanks for the tips.

On Monday, November 11, 2013 6:20:24 PM UTC, Alex Burgel wrote:
>
> Thanks for writing this up. I had been trying to figure this out myself.
>
> I think your reasoning is correct. There is also the case of deleting an 
> entity from one client and another client causing it to be added back to 
> memcache. _LOCKED should help in that case too. I think the key to all this 
> is the timeout duration, because if you have one very slow client, it could 
> still put old data into the cache.
>
> I came across some ndb issues that talk about some of these issues:
>
> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=17
> https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=84
>
> Also, I found this Facebook post on how they replaced memcache. It also 
> discusses similar issues:
>
> https://www.facebook.com/note.php?note_id=10151347090423920
>
> --Alex
>
> On Monday, November 11, 2013 10:25:24 AM UTC-5, Dan wrote:
>>
>> Having thought about this a bit, I think I understand why 
>> _LOCKED<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#27>
>>  needs 
>> to be used with NDB memcache to keep the datastore and memcache in sync 
>> within a transaction. FYI, NDB checks local memory then memcache and then 
>> the datastore for an entity.
>>
>> Suppose I implemented the naive approach mentioned above. I clear out all 
>> memcached entities affected at the start of a transaction and then after 
>> the transaction succeeds I repopulate memcache with the updated entities. 
>> This method *would* give stale data if memcache fails to repopulate at 
>> the end of the transaction.
>>
>> For example, if I have an entity MyEntity{int_property: 0} and I want to 
>> increment int_property by 1 transactionally.
>>
>>
>>1. Starting point: MyEntity{int_property: 0}  is in memcache and the 
>>datastore.
>>2. Transaction begins.
>>3. Delete MyEntity{int_property: 0} from memcache.
>>4. Get MyEntity{int_property: 0} from datastore.
>>5. Put MyEntity{int_property: 0} to MyEntity{int_property: 1}
>>6. Transaction succeeds.
>>7. Place MyEntity{int_property: 1} into memcache.
>>
>> What happens if between the start and end of the transaction, an external 
>> Get request repopulates memcache with MyEntity{int_property: 0}. That's 
>> fine because step 7 will overwrite that memcache entity when the 
>> transaction succeeds. However, what if step 7 *fails*? Everyone will be 
>> reading stale values (MyEntity{int_property: 0}) from memcache despite the 
>> transaction succeeding.
>>
>> I imagine _LOCKED is used to prevent this from happening:
>>
>>1. Starting point: MyEntity{int_property: 0}  is in memcache and the 
>>datastore.
>>2. Transaction begins.
>>3. Lock MyEntity{int_property: 0} key in memcache.
>>4. Get MyEntity{int_property: 0} from datastore.
>>5. Put MyEntity{int_property: 0} to MyEntity{int_property: 1}
>>6. Transaction succeeds.
>>7. Unlock MyEntity key from memcache and place MyEntity{int_property: 
>>1} into it.
>>
>> With this method a Get request external to the transaction will go 
>> straight to the datastore for its entity as it will see that memcache is 
>> locked. The important bit is that if the transaction succeeds in step 6 but 
>> memcache Set fails in step 7 we have no problem of data consistency as all 
>> Get requests will still see the memcache lock and use the underlying 
>> datastore. The unfortunate side effect is that memcache will be out of 
>> service for that entity however I see a 
>> _LOCK_TIME<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#26>
>>  variable 
>> which will timeout memcache after a reasonable period in order to put it 
>> back in action.
>>
>> I know I could probably just use pdb and step through NDB but it is more 
>> fun to figure it out for myself. Anyone know if I am on the right track 
>> with this?
>>
>> My motivation is that the Go SDK saves me money on instances but loses me 
>> money on datastore access. There are several Go libraries around but none 
>> of them seem to b

[google-appengine] Re: NDB strategy for keeping caches in sync with the datastore

[Dan]

Having thought about this a bit, I think I understand why 
_LOCKED<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#27>
 needs 
to be used with NDB memcache to keep the datastore and memcache in sync 
within a transaction. FYI, NDB checks local memory then memcache and then 
the datastore for an entity.

Suppose I implemented the naive approach mentioned above. I clear out all 
memcached entities affected at the start of a transaction and then after 
the transaction succeeds I repopulate memcache with the updated entities. 
This method *would* give stale data if memcache fails to repopulate at the 
end of the transaction.

For example, if I have an entity MyEntity{int_property: 0} and I want to 
increment int_property by 1 transactionally.


   1. Starting point: MyEntity{int_property: 0}  is in memcache and the 
   datastore.
   2. Transaction begins.
   3. Delete MyEntity{int_property: 0} from memcache.
   4. Get MyEntity{int_property: 0} from datastore.
   5. Put MyEntity{int_property: 0} to MyEntity{int_property: 1}
   6. Transaction succeeds.
   7. Place MyEntity{int_property: 1} into memcache.
   
What happens if between the start and end of the transaction, an external 
Get request repopulates memcache with MyEntity{int_property: 0}. That's 
fine because step 7 will overwrite that memcache entity when the 
transaction succeeds. However, what if step 7 *fails*? Everyone will be 
reading stale values (MyEntity{int_property: 0}) from memcache despite the 
transaction succeeding.

I imagine _LOCKED is used to prevent this from happening:

   1. Starting point: MyEntity{int_property: 0}  is in memcache and the 
   datastore.
   2. Transaction begins.
   3. Lock MyEntity{int_property: 0} key in memcache.
   4. Get MyEntity{int_property: 0} from datastore.
   5. Put MyEntity{int_property: 0} to MyEntity{int_property: 1}
   6. Transaction succeeds.
   7. Unlock MyEntity key from memcache and place MyEntity{int_property: 1} 
   into it.

With this method a Get request external to the transaction will go straight 
to the datastore for its entity as it will see that memcache is locked. The 
important bit is that if the transaction succeeds in step 6 but memcache 
Set fails in step 7 we have no problem of data consistency as all Get 
requests will still see the memcache lock and use the underlying datastore. 
The unfortunate side effect is that memcache will be out of service for 
that entity however I see a 
_LOCK_TIME<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#26>
 variable 
which will timeout memcache after a reasonable period in order to put it 
back in action.

I know I could probably just use pdb and step through NDB but it is more 
fun to figure it out for myself. Anyone know if I am on the right track 
with this?

My motivation is that the Go SDK saves me money on instances but loses me 
money on datastore access. There are several Go libraries around but none 
of them seem to be as rigorous or useful as NDB. After having tried several 
of them I am back to using "appengine/datastore" and slowly crafting each 
datastore hotspot which is a pain and error prone.


On Wednesday, November 6, 2013 8:09:31 PM UTC, Dan wrote:
>
> Would someone be able to explain to me the strategy that NDB uses to keep 
> its memory, memcache and datastore entities in sync and consistent 
> (especially during transactions)?
>
> I can't quite figure out from the 
> code<https://code.google.com/p/appengine-ndb-experiment/> what 
> goes on.
>
> For example, before the start of a transaction, does NDB delete memory and 
> memcache entities that will be affected by the transaction and then 
> repopulate them if the transaction succeeds?
>
> I see reference to a 
> _LOCKED<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#27>
>  value 
> to lock memcache. What is this used for and what happens if the unlock 
> operation fails?
>
> Best wishes,
> Dan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] NDB strategy for keeping caches in sync with the datastore

[Dan]

Would someone be able to explain to me the strategy that NDB uses to keep 
its memory, memcache and datastore entities in sync and consistent 
(especially during transactions)?

I can't quite figure out from the 
code<https://code.google.com/p/appengine-ndb-experiment/> what 
goes on.

For example, before the start of a transaction, does NDB delete memory and 
memcache entities that will be affected by the transaction and then 
repopulate them if the transaction succeeds?

I see reference to a 
_LOCKED<https://code.google.com/p/appengine-ndb-experiment/source/browse/ndb/context.py#27>
 value 
to lock memcache. What is this used for and what happens if the unlock 
operation fails?

Best wishes,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] How to implement publish/subscribe broadcast functionality with the Channel Service?

[Dan]

I would like to broadcast one message to a 'channel' and have many 
subscribers get updated in real-time using the App Engine Channel Service. 
How can I do this?

The Channel 
Service 
send_message(client_id, 
message) is only intended to be used to send *one* message to *one* client 
at a time.

My current implementation uses memcache to store a key which is my 
channel_id and list of values which are Channel Service client_ids. When I 
want to broadcast to a channel_id, I get the list of client_ids from 
memcache and call send_message(client_id, message) for each of them.

The implementation is currently written in Python and to optimise I do the 
following:
- Use marshal instead of pickle to store the list of client_ids in memcache.
- Use a frontend request (not a Task Queue) to call send_message(client_id, 
message) because Task Queues often seem to have large delays between being 
called and execution.
- Call each send_message(client_id, message) on a separate thread.

This works quite well when broadcasting to 10 - 20 client_ids and I don't 
mind too much that the memcache mapping from channel_id to client_ids could 
be evicted at any point (so long as the memcache service does not go down 
completely). However the multiple calls to send_message(client_id, message) 
start to introduce too much latency for more client_ids. I don't mind 
average latency up to 1.5 seconds.

How can I scale to 100 - 500 client_ids listening to one channel_id?

My initial thought was to use mapreduce map to fan-out but that is way too 
heavy and therefore expensive, plus it uses Task Queues so is prone to 
latency spikes when the tasks don't get executed in a timely manner.

My next thought was:
Have an entity type for each channel_id.

class Channel[channel_id](ndb.Model):
pass

Use client_id as the key for each client that is subscribed to 
Channel[channel_id].

Use the special __scatter__ 
propertyof
 each entity to shard groups of client_ids into separate memcache 
entities. (I realise for my scale __scatter__ is unlikely to be populated.)

Have one memcache entity containing all the __scatter__ ids.

Create a publish(channel_id, message) function that fans out URLFetch to 
frontend instances for each __scatter__ value. Each frontend request will 
in turn look up the memcache entity for their __scatter__ id and call 
send_message(client_id, message) for each client_id.

If everything worked smoothly with no memcache evictions, the datastore 
would not need to be touched most of the time. Would the Go runtime be best 
for implementing this most efficiently?

Alternatively does anyone know of a good push service that has a decent 
free quota and only charges what is used beyond that. I can't find one 
after looking for months. I see PubNub's free quota is too small (20 peak 
connections) and I am loathed to pay $14 per month for going over the quota 
by only a small amount probably 10 times per month. Or does anyone know of 
some code that does what I want already out in the public domain?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Sunsetting double wildcard SSL certificate support for applications serving from appspot.com

[Dan]

How does this affect modules? I see the modules 
documentation 
says 
they can be accessed by 
 http[s]://mobile-frontend.simple-sample.appspot.com for example. However 
if I access a module with https I get an invalid certificate error. 

Am I missing something or is there an error with the documentation? I have 
created 
issue https://code.google.com/p/googleappengine/issues/detail?id=9752 just 
in case there is.


On Thursday, January 10, 2013 11:47:15 PM UTC, Christina Ilvento wrote:
>
> *Hi All,*
> *
> *
> *As part of our continued commitment to security and a standard platform, 
> Google App Engine will soon stop publishing double wildcard SSL 
> certificates for *.*.appspot.com, (e.g., 
> https://version.application.appspot.com  or 
> https://www.application.appspot.com).
>  
> This change will take effect no later than April, 2013. Please note that 
> this only affects applications serving from appspot.com, and that any 
> applications serving from custom domains will continue using their existing 
> certificates. Furthermore, this only affects HTTPS access to your 
> application and non-secure HTTP traffic will not be affected.
>
> If you rely on HTTPS access to such URLs for your application, please 
> change any application logic to use "-dot-" instead of ".". For example, to 
> access version "1" of application "myapp" use "
> https://1-dot-myapp.appspot.com"
>  
> instead of "https://1.myapp.appspot.com";. 
>
> Developers for applications using this pattern as of 1/7/2013 have already 
> received a notification email with instructions for identifying this 
> pattern in their application.
>
> Based on our analysis, fewer than 2,000 App Engine applications are 
> currently using double wildcard SSL certificates on appspot.com and the 
> majority of them are using the pattern of https://www.appid.appspot.com, 
> which can safely be replaced with https://appid.appspot.com.
>
> Thank you for your continued support of App Engine. If you have any 
> questions or concerns about these changes, please feel free to email us at 
> appengine-ssl-certificate-wildcard-questi...@google.com with 
> your application-id and we'll be happy to assist you.
>
>
> Regards,
> Christina Ilvento on behalf of the Google App Engine Team
> *
>
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] SendGrid Integration

[Dan Holevoet]

Hi Joshua,

It was just announced this morning. More details here:
http://googlecloudplatform.blogspot.com/2013/07/sendgrid-gives-app-engine-developers.html

Thanks,
Dan


On Wed, Jul 24, 2013 at 1:22 PM, Joshua Smith wrote:

> Dunno how I missed this, but given the train wreck of GAE's email
> delivery, this is very promising:
>
> https://developers.google.com/appengine/articles/sendgrid
>
> -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 http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Google Oauth Javascript immediate:“true” NOT WORKING

[Dan Holevoet]

I've commented on your Stack Overflow post (
http://stackoverflow.com/questions/17017180/google-oauth-javascript-immediatetrue-not-working).
Can you follow-up there?


On Tue, Jun 11, 2013 at 1:31 PM, Gana  wrote:

> I am trying to use google endpoints. I have multiple page applicaiton. The
> user logs in using google auth javascript apis. I am using
> https://developers.google.com/api-client-library/javascript/reference/referencedocs#gapiauthauthorize
>
> On the subsequent pages I need to get the access token values, so I can
> call the google endpoints with the access token set along with the request.
>
> As per the documentation, its adviced to use immediate:true, but nothing
> comes up with that flag. It works with immediate:false, but that comes up
> with a pop up window. It will be annoying to the users to get pop up window
> on each screen as my user navigates across each page
>
> I refered to this sample applicaiton
> https://google-api-javascript-client.googlecode.com/hg/samples/authSample.html,
> after succesful login /autherize, if I come back to this application, it is
> showing up the authorize button and I have to hit it (pop up shows) to get
> authorized.
>
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Google Cloud Endpoints Without SSL

[Dan Holevoet]

Hi Isaac,

Endpoints requires SSL. There haven't been (and are unlikely to be) any
plans to change this. If you need to access your API in a system not
supporting SSL, you'll need to either update the system to support SSL or
run through a proxy.

Thanks,
Dan


On Fri, Jun 7, 2013 at 11:19 AM, Isaac Lañado  wrote:

> Hi All,
>
> I'm trying to create a web-service with Google App Engine (GAE) and the
> Google Cloud Endpoints using Java. I've just created a simple example which
> retrieves a simple text and it works perfect.
>
> The problem that I'm having is that when I upload it to GAE and access the
> web-service through HTTP i get the following messege from the json response
>
> {"error":{"errors":[{"domain":"global","reason":"sslRequired","message":"SSL 
> is required to perform this operation."}],"code":403,"message":"SSL is 
> required to perform this operation."}}
>
>
> and when I access through HTTPS i do get the right response
>
> {
>  "Text": "Hello world! from lanado's computer",
>
>  "kind": "test#helloWorldEndpointItem",
>
>  "etag": "\"D2SOFqEdwN1r8G-XCKxgVNRrWR0/izo2v_k7CeWU238fP57lIflWlHE\""
> }
>
>
>
> The thing is i really do need to access the web-service through HTTP since
> I'm connectig directly from a ORACLE XE database.
>
> Thanks in advance
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] want to migrate to python 2.7 from 2.5,but after making changes website doesn't work

[Dan Holevoet]

Hi Sam,

It looks like you've already asked this identical question, and haven't
provided any additional information in this second thread. Given the
technical question and answer format of your post, I'd suggest asking the
same on Stack Overflow. Make sure to provide additional details such as the
exact error message you are receiving on your site.

Thanks,
Dan


On Mon, Jun 3, 2013 at 1:50 PM, Sam Mak  wrote:

> I am trying to migrate from python to 2.7 to 2.5 but after making the
> required changes to main.py and app.yaml file, my site does not work
>
> please help... what changes should i make to these to get it to work
>
> main.py
>
> import os
> from google.appengine.ext import webapp
> from google.appengine.ext.webapp import util
> from google.appengine.ext.webapp import template
>
> class MainHandler(webapp.**RequestHandler):
>   def get (self, q):
> if q is None:
>   q = 'index.html'
>
> path = os.path.join (os.path.dirname (__file__), q)
> self.response.headers ['Content-Type'] = 'text/html'
> self.response.out.write (template.render (path, {}))
>
> def main ():
>   application = webapp.WSGIApplication ([('/(.*html)?', MainHandler)],
> debug=True)
>   util.run_wsgi_app (application)
>
> if __name__ == '__main__':
>   main ()
>
>
>
> app.yaml
>
> application: cool-gadgets
> version: 1
> runtime: python
> api_version: 1
>
>
>
> handlers:
> - url: /robots.txt
>   static_files: static/robots.txt
>   upload: static/robots.txt
>
> - url: /favicon.ico
>   static_files: static/favicon.ico
>   upload: static/favicon.ico
>
> - url: /gadgets/disney.xml
>   static_files: gadgets/disney.xml
>   upload: gadgets/disney.xml
>
> - url: /gadgets/wwe.xml
>   static_files: gadgets/wwe.xml
>   upload: gadgets/wwe.xml
>
> - url: .*
>   script: main.py
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] How to set deadline for a PHP URL fetch?

[Dan Holevoet]

This is a great question for the App Engine Stack Overflow
tag<http://stackoverflow.com/questions/tagged/google-app-engine>,
which also conveniently happens to have an
answer<http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-urlfetch-in-google-app-engine>for
you!

Thanks,
Dan


On Mon, Jun 3, 2013 at 8:20 AM, 1moretime  wrote:

> URL Fetch overview says:
>
> You can set a deadline for a request, the most amount of time the
> service will wait for a response. By default, the deadline for a fetch
> is 5 seconds. The maximum deadline is 60 seconds for HTTP requests and
> 10 minutes for task queue and cron job requests.
>
> Now, how can i set deadline to 60-sec ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Task Queue target parameter clarification

[Dan]

The documentation for the Task Queue target parameter for Python (
https://developers.google.com/appengine/docs/python/config/queue#target) 
states the following:

target (push queues only)
>
> The version of your application (including backends) on which the tasks in 
> this queue will be invoked.
>
> If unspecified, then tasks are invoked on the same version of the 
> application where they were enqueued. So, if you enqueued a task from the 
> default application version without specifying a target on the queue, the 
> task is invoked in the default application version. You can specify a 
> backend as your target.
>
What happens in the following scenario:
I have an app with version '12' as the default version and enqueue a task 
without using the target parameter.
I then change the default version to '13' before the task has executed.

Will the task execute on version '12' even though it is no longer the 
default version or will it execute on '13'? I believe it will still execute 
on version '12' but the documentation seems a bit ambiguous.

I would test on the SDK (v1.7.7) but using the target parameter has started 
producing errors queuing tasks with my current code so I have had to remove 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] [Python] Endpoints vs ProtoRPC ~200ms overhead

[Dan Holevoet]

Hi Alex,

No, I don't think you're doing it wrong. Your post encouraged me to find
out the results of our internal analysis, which came up similar to what you
were seeing. The good news is that there are a few different efforts
underway to chip away at the latency total. I can't give specifics, but
this is something we're working to improve.

I wouldn't expect Endpoints to be as fast as ProtoRPC, but hopefully we can
close the gap a bit. I also hope that the extra features provided by
Endpoints (currently, or in the future) will make it worth the latency hit.

Thanks,
Dan


On Mon, Apr 15, 2013 at 2:49 PM, alex  wrote:

> Hey, Dan. So, I basically took those numbers from logs of one of my
> apps (Python 2.7, threadsafe=true, SDK v1.7.7)
>
> I was looking at the logs the other day and noticed all Endpoints API
> calls were taking at least 200ms up to 400-500ms (well, I clearly had
> some Datastore and other stuff going on for it to be 500ms).
>
> I started experimenting and ended up with those two simple classes,
> EndpointsTest vs ProtoRpcTest, and TestMsg with the only msg string
> field.
>
> I then started calling their test method using curl (manually from a
> terminal) and watch the logs, for maybe 15-20 mins repeatedly with
> about 0.3-0.5 rps rate. I did the average in my head. Pretty easy - it
> never went lower than 200ms and higher than 270ms for
> EndpointsTest.test, and was in between 6ms-12ms for ProtoRpcTest.test.
>
> This was running an app in EU datacenters. I thought I'd try it with
> anothe app in US but got the same results.
>
> Maybe I was doing it all wrong. Actually, I'll be happy to hear that.
>
> Please let me know if this makes sense or I'm just comparing apples to
> oranges.
>
> On Mon, Apr 15, 2013 at 11:19 PM, Dan Holevoet
>  wrote:
> > Hi Alex,
> >
> > Can you share a bit more information about how you performed your tests?
> Are
> > those numbers averages? How many times did you call both APIs? Was this
> > repeatable or did you run the test multiple times?
> >
> > Thanks,
> > Dan
> >
> >
> > On Sat, Apr 13, 2013 at 1:46 AM, alex  wrote:
> >>
> >> I'm not sure it's even possible (to reduce the overhead), and I do
> >> understand there's another infrastructure layer that uses ProtoPRC lib,
> but
> >> still comare this:
> >>
> >> @endpoints.api(name='test', version='v1')
> >> class EndpointsTest(remote.Service):
> >>   @endpoints.method(VoidMessage, TestMsg)
> >> def test(req):
> >>   return TestMsg(msg='Hello there')
> >>
> >> curl /test/v1/test
> >> {msg:'Hello there'}
> >>
> >> - results in at least 200ms
> >>
> >>
> >> to this:
> >>
> >> class ProtoRpcTest(remote.Service):
> >>   @remote.method(VoidMessage, TestMsg)
> >>   def test(req):
> >> return TestMsg(msg='Hello there')
> >>
> >> curl -X POST /prototest.test
> >> {msg:'Hello there'}
> >>
> >> - results in about 7-10ms
> >>
> >>
> >> There seem to be a few additional roundtrips going on when making
> requests
> >> via Endpoints.
> >> Do you guys think it's possible to reduce the latency?
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Google App Engine" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to google-appengine+unsubscr...@googlegroups.com.
> >> To post to this group, send email to google-appengine@googlegroups.com.
> >> Visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >>
> >
> >
> >
> >
> > --
> > Dan Holevoet
> > Google Developer Relations
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to google-appengine+unsubscr...@googlegroups.com.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > Visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> You received this message because you are subscribed t

Re: [google-appengine] [Python] Endpoints vs ProtoRPC ~200ms overhead

[Dan Holevoet]

Hi Alex,

Can you share a bit more information about how you performed your tests?
Are those numbers averages? How many times did you call both APIs? Was this
repeatable or did you run the test multiple times?

Thanks,
Dan


On Sat, Apr 13, 2013 at 1:46 AM, alex  wrote:

> I'm not sure it's even possible (to reduce the overhead), and I do
> understand there's another infrastructure layer that uses ProtoPRC lib, but
> still comare this:
>
> @endpoints.api(name='test', version='v1')
> class EndpointsTest(remote.Service):
>   @endpoints.method(VoidMessage, TestMsg)
> def test(req):
>   return TestMsg(msg='Hello there')
>
> curl /test/v1/test
> {msg:'Hello there'}
>
> - results in at least 200ms
>
>
> to this:
>
> class ProtoRpcTest(remote.Service):
>   @remote.method(VoidMessage, TestMsg)
>   def test(req):
> return TestMsg(msg='Hello there')
>
> curl -X POST /prototest.test
> {msg:'Hello there'}
>
> - results in about 7-10ms
>
>
> There seem to be a few additional roundtrips going on when making requests
> via Endpoints.
> Do you guys think it's possible to reduce the latency?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Package name error in app engine connected android project after endpoint library generation

[Dan Holevoet]

There's an issue filed in the Google Plugin for Eclipse tracker which you 
can 
follow: https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=117

On Friday, April 12, 2013 11:55:01 AM UTC-7, Simon Hirscher wrote:
>
> Generating Endpoint client library fails with strange package name error 
> (s. error.png). Is this a known issue? 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Deploy appengine endpoints to non-default version

[Dan Holevoet]

Hi Miguel,

Unfortunately, the ability to deploy Endpoints to non-default app versions
still isn't available. The required SDK code should be in 1.7.6+, but
awaits a change on the backend to take effect. I'll post an update when
it's live.

Thanks,
Dan


On Fri, Apr 5, 2013 at 7:58 AM, Miguel Sanz  wrote:

> According to the trusted tester documentation, there was an issue with
> endpoints that prevented them to be created when deploying to a
> "non-default" version. When 1.7.5 was released and endpoints graduated from
> trusted tester to "Experimental" we were told that this issue was fixed but
> couldn't be included in 1.7.5 (for timing reasons) and would be included in
> the next version.
>
> Ok, the next version is already here (1.7.6) but still, if I deploy
> endpoints to a non-default version, they are not generated. Does anybody
> know if there is some specific setting that needs to be added to web.xml,
> appengine-web.xml or somewhere else? Or is this just that this feature was
> not included in 1.7.6 either.
>
> From my point of view this is essential. I have an Android app based on
> requestfactory. If I replace my default version, the app will stop working.
> I need to deploy to a separate version, deploy a new Android app version
> pointing to this server version, and after some time when most of users
> have updated their Android app set that as default.
>
> Thanks for any hints on 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] How to fan out URL fetch requests in a timely fashion?

[Dan]

Hi Jeff,

Thanks for the reply. I think fanning out 10 async urlfetches to my own 
app's front end which in turn calls 100 url fetches each is a great idea. I 
am not too concerned about cold starts as I am using a small python code 
base and in any case as you suggested, I could have a separate version 
running Go to do the fanout.

One hurdle though is that each remote client callback url is stored in a 
separate datastore entity. I would have used DatastoreInputReader from the 
Pipeline API to automatically get batches of entities. I understand that 
the DatastoreInputReader uses a hidden property '__scatter__' (
https://code.google.com/p/appengine-mapreduce/source/browse/trunk/python/src/mapreduce/input_readers.py#563)
 to 
help with the sampling of entity key ranges. I wonder how I could achieve 
the same thing in order to break my 1000 datastore/memcache calls into 10 
roughly equal batches of 100? Maybe I should take the risk and just use 
'__scatter__' and hope no one changes it... ;-)

On Sunday, April 7, 2013 6:00:45 PM UTC+1, Jeff Schnitzer wrote:
>
> Have you figured out what kind of throughput you get if you run 1000 
> async urlfetches?  GAE will only process 10 simultaneously, but as 
> long as each completes in avg 50ms you'll make your 5s goal. I suspect 
> this is unrealistic but it would be good to know the baseline 
> performance. 
>
> Consider running 10 async urlfetch requests to your own GAE app, each 
> of which then launches 100 async urlfetches. Here you will likely run 
> into problems with the # of instances you have available; as soon as 
> one of these requests goes to a cold start you may be hosed. You could 
> implement these fanout instances as a special version (or different 
> appid) implemented in Go, which may take care of the startup time - 
> test it. 
>
> Or you could just run a Node.js server somewhere in another cloud 
> (ideally Google Compute Engine if you can get access) and let it do 
> the fanout. You might even get 1k requests out of a single box in the 
> allotted time period. 
>
> Looking for a service to do this is overthinking it. At worst, run 
> your own service; this is less than a dozen lines of Node.js. 
>
> Jeff 
>
>
> On Sun, Apr 7, 2013 at 12:07 PM, Dan > 
> wrote: 
> > Every minute or so my app creates some data and needs to send it out to 
> more than 1000 remote servers via URL Fetch callbacks. This is done 
> asynchronously using NDB. The time lag between creating the data and 
> sending it to the remote servers via the callback should be roughly less 
> than 5 seconds. 
> > 
> > My initial thought is to use the Pipeline API to fan out URL Fetch 
> requests to different task queues. 
> > 
> > Unfortunately task queues are not guaranteed to be executed in a timely 
> fashion. Therefore from requesting a task queue start to it actually 
> executing could take minutes to hours. From previous experience this gap is 
> regularly over a minute so is not necessarily appropriate. 
> > 
> > Is there any way from within App Engine to achieve what I want? Maybe 
> you know of an outside service that can do the fan out in a timely fashion? 
> > 
> > The question is on Stack Overflow: 
> > 
> > 
> http://stackoverflow.com/questions/15829813/how-to-fan-out-url-fetch-requests-in-a-timely-fashion
>  
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Google App Engine" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to google-appengi...@googlegroups.com . 
> > To post to this group, send email to 
> > google-a...@googlegroups.com. 
>
> > Visit this group at 
> http://groups.google.com/group/google-appengine?hl=en. 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] How to fan out URL fetch requests in a timely fashion?

[Dan]

Every minute or so my app creates some data and needs to send it out to more 
than 1000 remote servers via URL Fetch callbacks. This is done asynchronously 
using NDB. The time lag between creating the data and sending it to the remote 
servers via the callback should be roughly less than 5 seconds.

My initial thought is to use the Pipeline API to fan out URL Fetch requests to 
different task queues.

Unfortunately task queues are not guaranteed to be executed in a timely 
fashion. Therefore from requesting a task queue start to it actually executing 
could take minutes to hours. From previous experience this gap is regularly 
over a minute so is not necessarily appropriate.

Is there any way from within App Engine to achieve what I want? Maybe you know 
of an outside service that can do the fan out in a timely fashion?

The question is on Stack Overflow:

http://stackoverflow.com/questions/15829813/how-to-fan-out-url-fetch-requests-in-a-timely-fashion

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Endpoint Error & Stuck, about to take alternate routes :(

[Dan Holevoet]

Hi Gana,

Have you asked this question on Stack Overflow (and provided code?)

Thanks,
Dan


On Fri, Mar 22, 2013 at 6:02 AM, javabuddy  wrote:

>
> After much struggle and lot of local testing created my endpoint
> applicaiton, but once I deploy to app engine I getting the following error.
>
> https://ganatest6.appspot.com/_ah/api/taskandtest/v1/alerts?username=g
>
> {
>  "error": {
>   "errors": [
>{
> "domain": "global",
> "reason": "internalError",
> "message": "Internal Error"
>}
>   ],
>   "code": 500,
>   "message": "Internal Error"
>  }
> }
>
>
> Is endpoints not ready for Production?? If so I am stuck and need to find 
> alternate ways.
>
>
> Please help.
>
>
>
> -Gana
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Encryption seling data

[Daniel Dan Iosif]

 






   In need a simple solution to manage a loyalty system for 14 difrent 
Beauty Salon.

is a association that wants to use in commun PVC card with barcode ID.


1.What is simple solution to create a app for selling and to manage loyaty 
sistem ? to run in online/offline mode 

Loyaty card is commun but selling is privat for each store.


2 .Is posible to save on local selling and to upload just loyaty 
information ?

3.Is posible a simple encryption for seling data ?

4.What arguments and solutions that can be useful for the client to be 
convisn that nobody sees sales data ?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Search API: How to find the closest document?

[Dan]

I am trying to use the Search API to find the closest document to specific 
GeoPoints located anywhere on the globe.

My documents are distributed in dense clusters (>1000 documents in a 10km 
radius) with big gaps between the clusters (>4000km).

I am getting incorrect results with the Search API and would like to know how 
to fix the problem. 

More details of my issue are at 
http://stackoverflow.com/questions/15254983/how-can-i-find-the-closest-document-using-google-app-engine-search-api

I am getting no response on StackOverflow so thought I would cross post here.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Cannot activate billing

[Dan Holevoet]

Hi,

Can you check out the FAQs here (
https://developers.google.com/appengine/kb/billing), and if those aren't
helpful, fill out this billing help form?
https://developers.google.com/appengine/kb/billing#morehelp

Thanks,
Dan


On Sun, Feb 3, 2013 at 1:53 AM,  wrote:

> I have been trying to activate billing for almost 1 day.
>
> My google wallet account says that it is ok and my applications status
> becomes activating billing.
> About 2 hours later my application status again becomes free.
>
> Can anyone help me?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] GAE down ?

[Dan Holevoet]

Hi Francois,

The status page was updated a few minutes ago with a message that we're
investigating the issue. We'll update as we have more information.

Thanks,
Dan


On Thu, Jan 31, 2013 at 2:12 PM, Francois Masurel wrote:

> Hey Google, what is going on ?  Status 
> page<http://code.google.com/status/appengine/> has
> been showing "Anomaly" state for a few minutes already.
>
> Most of my customers web sites hosted on my GAE app (vncts1) are down or
> only half loading.
>
> New instances are started every few seconds and killed almost immediately.
>
> My app doesn't have enough time to get fully initialized (it usually takes
> less than 8s).
>
> And last outage was only few days ago...
>
> François
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Dan Holevoet
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.