Re: [google-appengine] Re: domain is blocked

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

I think that the steps and troubleshooter linked here 
 would be a better 
place to start. Folks in GCP Support are not likely to be able to make 
changes to GMail deliverability.

On Monday, December 2, 2019 at 1:37:44 PM UTC-5, Pierre-Yves Blain wrote:
>
> Hello,
>
> since your question requires more specific troubleshooting I would advise 
> to post your inquiry on https://developers.google.com/issue-tracker.
> Google Groups is used to discuss higher-level concepts, where Issue 
> Tracker is used for bugs and situations which require specific 
> troubleshooting. Additional information may be required privately to 
> correlate your domain to the GCP project and App Engine instances linked to 
> the domain.
>
> On Thursday, November 28, 2019 at 12:30:43 PM UTC-5, Ярик Швиденко wrote:
>>
>> mail.ngu.gov.ua
>>
>> чт, 28 нояб. 2019 г. в 17:37, Ярик Швиденко :
>>
>>> Hi Elliott. The domain name of my mail service is ngu.gov.ua. Gmail 
>>> blacklisted it after spamming mail started on its behalf. This happened 
>>> during the firewall replacement. For a while the service became available 
>>> on many ports, after which we were hacked.
>>>
>>>
>>>
>>> ср, 27 нояб. 2019 г. в 01:34, 'Elliott (Cloud Platform Support)' via 
>>> Google App Engine :
>>>
 Hello,

 Can you tell me more about your domain and how it is being blocked? 
 When did this start? We need this to have basic information.

 -- 
 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/51550208-ca64-4386-bfe4-f0aa90b10d4c%40googlegroups.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f211b197-bba3-4b04-b661-6a425b9329b2%40googlegroups.com.

[google-appengine] Re: Disable weak cipher for Google Cloud App engine custom domain website

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Samuel,

You're completely correct that the requirements change in June, but for now 
the PCI Security Standards Council seems to consider 3DES to be "strong 
security."  Given 
that June is only a few months away, security consultants are 
understandably interested in knowing more about the transition plan. Thus 
this thread.

First, for future readers: "[t]he PCI Attestation of Compliance for Google 
Cloud Platform is shared with customers under NDA. 
" If you need more 
details, reach out to the sales team  to 
get the relevant documentation. You don't need a support contract for this.

Now to your question, I don't know (and given the NDA requirement probably 
couldn't share) what specific changes will be made ahead of the new 
requirements. If having those specifics is important, please reach out to 
the sales folks. If getting ahead of the requirements is important, then go 
ahead and file a ticket with technical support now.

Regards,
Jesse

On Wednesday, April 4, 2018 at 3:35:05 AM UTC-4, Samuel Melrose wrote:
>
> Thanks guys from Google Cloud Support.
>
> I have to ask though - we have 15+ custom domains across multiple 
> different apps, all of which have to be PCI-DSS compliant.
>
> Are you saying the platform won't be compliant by default? (by having the 
> weak cipher enabled and suggesting it has to be disabled manually per 
> domain, plus by the end of June, TLSv1.2+ only will be a requirement).
>
> We chose App Engine for the out of the box PCI-DSS compliance, but this 
> thread seems to be suggesting otherwise.. ??
>
> We do have Gold support so I will open this privately closer to the 
> deadline, but for the benefit of others who may have the same issue, it 
> would be great if we could get an answer here.
>
> On Tuesday, April 3, 2018 at 10:15:05 PM UTC+1, Fady (Google Cloud 
> Platform) wrote:
>>
>> As to update this community thread, working with Nikolaus, and the 
>> Engineering team we were able to disable the cipher (3DES) for his custom 
>> 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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c4d2329b-9182-438a-83c1-0a3e26d563a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Disable weak cipher for Google Cloud App engine custom domain website

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

One aside: I'm curious where Google suggests that App Engine should not be 
PCI-DSS compliant; this seems like a documentation issue that we should fix.

On Thursday, March 22, 2018 at 4:30:16 AM UTC-4, Samuel Melrose wrote:
>
> Thankfully, if using Cloudflare Enterprise, you can enable TLSv1.2+ only 
> and they move you to a different set of IP ranges to support this.
>
> I'm curious why Google are suggesting that App Engine shouldn't be PCI-DSS 
> compliance, since their site states it is, as well as being sold that way 
> by their account managers:
>
> https://cloud.google.com/security/compliance/pci-dss/
>
> Are they going to remove that come June 30th when TLSv1.2+ becomes a 
> requirement, or they won't stop supporting the old ciphers on App Engine at 
> the GFE?
>
> On Thursday, March 22, 2018 at 5:46:36 AM UTC, Attila-Mihaly Balazs wrote:
>>
>> AFAIK cloudflare has that same cipher (as a very last resort - just like 
>> Google - so realistically 99.999% of the clients won't use it): 
>> https://github.com/cloudflare/sslconfig/blob/master/conf
>>
>> So, yeah, "auditors".
>>
>

-- 
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/dd2f0ef8-207c-40be-ac05-e4cc2199d9c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: I signed up for a free trial and yet my credit card is being charged. Why? How do I contact Google and ask them to include it in my free credit?

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Our colleagues on the billing support team can help you 
out: https://support.google.com/cloud/contact/cloud_platform_billing

-- Jesse

On Tuesday, January 23, 2018 at 9:18:16 AM UTC-5, Aseem Yash wrote:
>
> I signed up for a free trial and yet my credit card is being charged.
> Is there any way where I can make google include the remaining costs in my 
> free trial credits?
>

-- 
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/3525890e-7484-4488-9b36-6794d3e6784b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: What is the google issue tracker process.

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Hi Toby,

On Tuesday, August 1, 2017 at 1:51:18 PM UTC-4, Torbjørn Smørgrav wrote:
>
> I've reported a problem with Java8 that has been confirmed by the first 
> triage. Now three weeks has gone and I would like to know what I can expect 
> in terms of response to the ticket.
>

In this specific case, thank you for flagging. We escalated internally, 
which got us to notice that it was related to issue 64282261 

 

>
> Regardless of my current issue - what is the process for issues?
>
> * How many levels of triage is there? 
>

My colleagues on the support team triage issues and file them with the 
appropriate engineering team. Beyond there, the details of triage are 
really down to the individual team's process, so I cannot answer in general 
terms. But if it helps your mental model, at least two, of which the first 
phase is largely about collecting lot of information while the bug is fresh 
then getting a corresponding bug to the right team.
 

> * Do the various priorities have an SLA?
>

They do not. I'm not sure that we are systematically setting priorities on 
new issues, though the ones imported from Google Code had priority settings 
all over the map, largely because users could just set label to give an 
issue a new priority. 
 

> * Will a ticket be designated some state so I can reason about if I can 
> wait for the fix or not (e.g. won't fix, or later)?
>

For defect reports, yes. Right now that process is manual and delay-prone, 
so we're looking at some automatic state synchronization.

For nontrivial feature requests that question is much less clear, since 
it's very common for what seems like a standalone feature request to be 
tied up with a much bigger initiative (which we tend not to disclose until 
it's in beta).
 

>
> Thanks,
> -Toby
>
>
Regards,
Jesse 

-- 
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/5fa014a3-cd1f-4b8c-aa9d-894ac34af2d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Hey George, this doesn't reproduce if you use your @google.com account, but 
I was just able to reproduce with my @gmail.com account. I don't yet know 
if the difference is because of @google.com accounts or because we have 
extra ACLs beyond the public.

I'm reaching out to the Buganizer/IssueTracker team now. 


On Monday, June 5, 2017 at 11:02:07 AM UTC-4, Dan Morris wrote:
>
> 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/fd2164ac-03db-49eb-86c1-733a41807f7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Sneaky machinations on the issue tracker

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Hello again Attila,

 

First off, I want to apologize. We did a bad job on the issue report you 
cite. It's already reopened and we're taking another look. Should something 
like this happen again in the future, posting here is a fine way to get us 
to take another look at an issue. Moreover, if we're giving incorrect 
information, we need to know, so that we can fix it.

 

That said, I want to assure you that we do not have bots closing issues. In 
this, case we closed the issue because we hadn't heard from you for a week, 
and at the time we thought we still needed more info from you.

 

Next, when it comes to reviewing new issues, I'm "the management," so I can 
be pretty confident in saying we do not encourage our staff to close 
issues: rather, we encourage them to triage them.

 

We offer the issue tracker because you shouldn't have to pay for support to 
report bugs, just like we offer several Google Groups because you shouldn't 
have to pay for general advice and discussion. Investigating possible new 
bugs, providing general advice, and answering questions on Stack Overflow 
-- these three channels are handled by the same team within Support -- 
scale to benefit all of our customers, so we can justify doing it for free, 
with a fixed-size team. But I'd be doing you a terrible disservice to 
pretend that we can provide SLAs (service level agreements, including 
guarantees on response time) on any of these one-to-many forums. If you 
need SLAs on support issues, check out this page 
 and appropriate links from it.

 

Regards,

Jesse Scherer

Technical Program Manager, Google Cloud Platform


On Friday, May 19, 2017 at 9:47:03 AM UTC-4, Attila-Mihaly Balazs wrote:
>
> So, yes, we basically need to find an ex-googler "consultant" who still 
> has relations with people working at the company to get the issues looked 
> at / fixed.
>

-- 
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/3bddf455-d4c3-4201-96db-9b15c6985aaa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Ongoing App Engine Commitment?

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Hi Tim, sorry for the late reply but I've been working on a novella for you 
:-)

I'm a technical program manager from the GCP support team. I work on 
community-facing support (which is just part of our support 
 offering) for all of GCP, including App 
Engine.

On Friday, March 31, 2017 at 8:39:29 AM UTC-4, Tim Consolazio wrote:
>
> I've been noticing some things:
>
- App Engine support shunted over to Stack Overflow (so...a non-Google 
> community resource).
>

It turns out that if you search for a particular error message from one of 
our products, you're very likely to see a Stack Overflow question about 
that very message among the first results. So yes, we lose some control, 
but the Stack Overflow community is pretty good at maintaining a high 
quality Q&A site. Given that our goal is for every interaction to help as 
many people as possible, it makes sense to go where the users are.

I should point out that we actively monitor this Google Group and bug 
reports on issuetracker.google.com, not just Stack Overflow. The difference 
is in focus: Stack Overflow is a place for "I know what I want to do, but 
not quite how" type Q&A.

- Mail API pretty much deprecated (no more quota expansions, 100 email 
> limit). 
>

You're right, that's not great. A while ago, Kim Lewandowski mentioned 
 
that we're investigating a solution to the issues that plague the current 
mail API. There's currently a thread going about this; please take Kim up 
on her offer 
 
to share use cases.
 

> - Deprecation of Channel API (sure we have Firebase, but still...what's 
> the commitment to that?)
>

Since I work for support and not product management I can only speak 
informally, but Firebase is a product with a lot of integrations across 
Google products. This isn't one I'd worry about. Also notice the byline 
 and linked article 
 on Firebase's homepage 
pointing out the integration of Firebase and Cloud Functions.
 

> - No Java 8 (and 7 was a long time in coming).
>

I think Jeff already covered this one :-)
 

> - Gradual deprecation of local SDK in favor of remote/virtual dev (which 
> to me is unacceptable, I depend on that local SDK). 
>

My colleague Justin Beckwith talked about this 
 
a few months ago: we understand that local development is an important 
feature and are looking at how to enable it in gcloud. But since it's not 
ready yet, we do continue to maintain the standalone SDK.
 

>
> I frequently recommend App Engine (and I've built quite a few apps on it). 
> I've been a rogue evangelist of the platform for years (since it was 
> released in fact), and have been contracted by Google three times to build 
> applications using it. So I'm not a hater in any way. 
>
> But I can't look at these events (particularly the Stack Overflow thing) 
> and ignore the impression that App Engine is beginning to feel more like a 
> side project rather than a commercial offering with full resource 
> commitment by the vendor. 
>

I've spoken to your point about Stack Overflow already, but I hope you're 
not reading too much into things like Datastore becoming a first-class 
product instead of an App Engine-only feature. That sort of transition 
acknowledges the reality there are several models for cloud compute, and 
that a lot of features which launched as part of App Engine (when App 
Engine was our sole compute offering) make just as much sense when used 
with containers, or VMs, or Cloud Functions.  
 

>
> Curious about a formal statement of commitment here, and a complete 
> roadmap of what we can reasonably expect over say, the next two years. 
>
>
We've mentioned this before, but there are a lot of reasons for us to be 
tight-lipped about our exact roadmap. But I hope that seeing real progress 
like the Flexible Environment exiting Beta or upcoming Java 8 on Standard 
 
demonstrate our commitment to App Engine.
 
Regards,
Jesse

-- 
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/12559c6a-764d-4084-a7e2-83a6c71297ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: !!!URGENT!!! CloudSQL Suspended after disable and re-enabling Billing

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Hi Lawrence, a few points:

First, I agree that it is odd that the billing team would ask you to come 
to the App Engine mailing list about a problem with Cloud SQL. Thank you 
for sharing your billing case number so that we can figure out what went 
wrong.

Second, I should explain our community support model:
- We (Cloud Platform Support) monitor this and several other mailing lists 
(including one for Cloud SQL) in order to provide help to as many people as 
possible. Our activity on these forums leans toward providing advice and 
pointing folks in the right direction.
- We also keep an eye out for people who have slipped through our normal 
support channels
- We monitor this mailing list only during North American business hours. 
And since I wrote the automation in question, I feel okay disclosing that 
the script which alerts us to new mailing list threads doesn't trigger on 
keywords in the thread.
- In parallel with our community support activities, we offer paid support 
contracts which carry an SLA around initial response time for critical 
issues. Depending on the nature of your business the cost of a support 
contract may be appropriate.

For you, the right direction seems (from what you've stated) to be the 
billing team. It also seems like your existing billing case wasn't handled 
well, and it's completely appropriate to escalate here.

Lastly, back to your original problem of the stuck Cloud SQL instance. I 
see that you opened issuetracker.google.com/issues/36290200. This is the 
right approach when you suspect a bug (as this might be, given how long ago 
you re-enabled billing), but we will need more information such as the 
instance that is stuck.

On Thursday, March 16, 2017 at 12:42:48 PM UTC-4, Lawrence Mok wrote:
>
> Hi Jordan,
>
> Case number for CloudSQL issue is:
>
> [#12317695] General Cloud Billing Query [] [ 
> ref:_00D00VNwG._5006015YLfd:ref ]
>
> If possible could you just start my instance first before fixing anything? 
> We had dozen of website depending on this database and now we cannot offer 
> all the services to our client and we cannot accept any payment from any 
> new clients too
>
> Thanks for your help
>
>
>
> On Thursday, March 16, 2017 at 11:55:16 PM UTC+8, Jordan (Cloud Platform 
> Support) wrote:
>>
>> Hey Lawrence,
>>
>> Could you provide the case number for the Billing Case you opened so that 
>> I can see your project information. As previously noted Google Groups is 
>> not for technical support and if they needed to route you (because your 
>> billing account is ok) it should have been either directly to technical 
>> support or to the the Issue Tracker 
>> . 
>>
>

-- 
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/a6ac2ba1-cbbc-4c4f-b7cb-3b5cb0168bb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Code issue trackers read-only

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

The issue trackers are back online, served from 
http://issuetracker.google.com. Please check our our blog post 
<https://cloudplatform.googleblog.com/2017/03/a-new-issue-tracker-for-Google-Cloud-Platformud.html>
 for 
more information.

On Thursday, March 2, 2017 at 12:22:43 PM UTC-5, Jesse Scherer (Google 
Cloud Support) wrote:
>
> Greetings all,
>
> We're marking the Google Code App Engine project read-only in order to 
> perform the migration to Google Issue Tracker 
> <http://developers.google.com/issue-tracker>, which will replace 
> <https://developers.google.com/issue-tracker/references/faq> Google Code 
> as the backend for public-facing issue trackers. While some mechanics will 
> change, all content will be preserved. When we're done, we'll set up 
> redirects so that old links to Google Code forward to to the corresponding 
> Issue Tracker issue.
>
> I'll post again when we're back!
>
> Regards,
> Jesse
>

-- 
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/df11c41c-dc05-4143-b723-6299b07c72c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google Code issue trackers read-only

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Greetings all,

We're marking the Google Code App Engine project read-only in order to 
perform the migration to Google Issue Tracker 
, which will replace 
 Google Code as 
the backend for public-facing issue trackers. While some mechanics will 
change, all content will be preserved. When we're done, we'll set up 
redirects so that old links to Google Code forward to to the corresponding 
Issue Tracker issue.

I'll post again when we're back!

Regards,
Jesse

-- 
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/3a2e6afb-1712-40f7-9c7d-890618e13bea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Linux Remote Desktop?

['Jesse Scherer (Google Cloud Support)' via Google App Engine]

Looks like he did 
, 
and our colleague Faizan pointed him toward some good material on Stack 
Overflow 
.
 
As an aside, I'm surprised that post hasn't been migrated to ServerFault 
(which is generally a better forum for configuration and administration 
questions).

Regards,
Jesse
 
On Thursday, July 14, 2016 at 6:55:46 PM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Hey Andrew,
>
> Could you clarify a bit what your set-up looks like? Which computers have 
> which OS's, how are you attempting to connect, what have you installed, how 
> have you configured what you've installed, what messages or information are 
> you seeing, etc.? 
>
> Also, just for information in future, this thread would probably be better 
> posted to the Compute Engine group 
> . In fact, you 
> still could do so, as it's more likely to find more helpful users there. 
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, July 14, 2016 at 11:23:54 AM UTC-4, Andrew Irwin wrote:
>>
>>
>> I can not figure out what I'm doing wrong, but I've tried a number of 
>> different Linux desktop remote clients, and have also tried mapping the 
>> xhost DISPLAY, however nothing I do is yielding a desktop? I just need to 
>> be able to connect to my x Windows and I've already loaded the GNOME & KDE 
>> desktop environments.
>>
>

-- 
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/d71e25ac-f690-40d0-a60a-d077b6c0bb5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Feedback to Google Technical Support on their contribution in this list

[Jesse Scherer (Google Cloud Support)]

Hello again PK, and thanks for your thoughts.

We're glad that having the technical support team more involved is making a 
noticeable difference, and your feedback is very helpful as we try to get 
better.

I want to elaborate on your point about the responses on this list. One of 
the things you see us doing -- redirecting users to other forums -- is very 
intentional. While this list is an appropriate (and encouraged) venue for 
open discussion, there are better platforms for specific programming 
 and system administration 
 questions, and we want to encourage people to use 
those when appropriate. This isn't because we want to ignore the question 
-- we answer a lot of questions on StackExchange sites as well -- but for 
visibility, which has two very different benefits for the user community at 
large.

First, we encourage people to move the appropriate questions to 
StackExchange sites in order to get you an answer faster: there are many 
more eyeballs on StackOverflow than in this mailing list; this attention 
means more chances for the help you need.

Second, the visibility of those questions and answers is a lot better on a 
Stack Exchange Q&A site than on this mailing list. A Google search for "App 
Engine eventual consistency 
"
 
demonstrates what I mean -- the first page is dominated by official docs 
and StackOverflow questions, not mailing list archives. We feel that if 
somebody (including us) is going to help you with a tough technical 
problem, that work should be as useful as possible, and that usefulness 
includes helping the next person who encounters the same issue.

You were also wondering whether our organization monitors for responses: we 
do, but not in the way you imply. Our aim is to be helpful and informative, 
not verbose. Simply put, if the direction of a conversation makes us think 
that we in the support org can give useful input, we give it. If it needs 
attention from a product manager or our legal team, we internally raise 
that flag. And if there's nothing we can do besides acknowledge that we 
heard you, we try to do that. Perhaps, in our attempts to improve on our 
prior "neglect" of the mailing lists, we're being too chatty, and we'll 
definitely keep that possibility in mind going forward.

Regards,

-- 
Jesse J. Scherer
Technical Program Manager, Google Cloud Support
jsche...@google.com

On Friday, October 16, 2015 at 6:05:18 PM UTC-4, PK wrote:
>
> Hi,
>
> Just a couple of thoughts I wanted to share for a while but two responses 
> in the list today triggered this.
>
> For a while now I see Google Technical Support monitoring this list and 
> responding to threads and this is very positive. For those of use who have 
> been with GAE for a long time, this is refreshing after the absolute 
> neglect that followed the early days with the participation of the 
> developers themselves.
>
> However, I see a pattern I do not like. I feel that at times you do reply 
> just so that you reply without adding a lot of value. For instance, many of 
> the very quick responses that can be summarized as “this is not the right 
> forum for this question” or today’s “I cannot tell you if this is a bug and 
> when will be fixed but programs break input into buffers and sometime they 
> do not properly reassemble them, so here you have an explanation” make me 
> wonder if they add any value or just help increase a metric of responses 
> your organization is monitoring.
>
> Again just my 2c,
> PK
> p...@gae123.com
>
> PS I suspect this is the wrong forum for this kind of feedback and 
> apologize 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6e309e11-a07e-436e-b9fe-6f9984e7213f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Custom Domains (and SSL)

[Jesse Scherer (Google Cloud Support)]

Hi Jay,

Since your question is about system administration and not programming, you 
might try ServerFault as opposed to StackOverflow.

In any case, can you share a bit more information? What does "Permissions" 
in the Developer console look like, for instance? Any other background you 
can share will help us (and folks on ServerFault) come up with better ideas.

Regards,

On Tuesday, September 29, 2015 at 7:24:49 AM UTC-7, Jay wrote:
>
> I'm not sure if this question is best here or Stackoverflow. 
> I am looking to use the feature recently moved to the google cloud console 
> to add an SSL certificate. We are already using a custom domain.
> Here is the new thing I ran into. When I log in and look at a particular 
> project, on which we already have a custom domain setup, I see nothing. It 
> looks like we have not set anything up. A colleague of mine logs in and 
> does the same thing, on the same project, and he sees a custom domain 
> already configured. This is before we get to the stage of setting up the 
> SSL.
>
> So we are seeing two different things. This makes me nervous. It also 
> means that I can't, apparently, setup the SSL, he would have to do that. 
> Surely, the configuration here is not tied to the user in some way. I must 
> be missing something.
>
> Thanks for any insight or suggestions.
>
> -- Jay
>

-- 
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/26748163-3ea4-4752-b3b4-f15cfd86bee5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Some instances running unreleased version of the App Engine SDK?

[Jesse Scherer (Google Cloud Support)]

Julian there should be somebody from the engineering team reaching out to 
you soon -- if not already -- to understand what happened in your case.

As I mentioned in PK's issue we're working on ways to handle canaries 
better. BTW the most obvious approach, a flag for "never run my app on a 
canary app server" is not that great because it would simply delay 
discovery of problems until the appserver version which works for you is no 
longer current.

On Thursday, September 17, 2015 at 6:32:17 PM UTC-4, Julian Bunn wrote:
>
> Thanks, PK - I will take a look at the issue you filed and comment 
> accordingly.
>
> We suffered pretty major disruption to our application, and lost many 
> hours of data, unfortunately. The symptoms were extra null fields in some 
> Datastore objects, which caused storage of new uploaded data from clients 
> to fail, and a greatly increased Error rate from our app. 
>
> Julian
>
>
>
> On Thursday, September 17, 2015 at 2:22:08 PM UTC-7, PK wrote:
>>
>> Hi Julian,
>>
>> Google routinely does this when they release a new runtime that they 
>> believe it is backwards incompatible. It mostly works OK but I did 
>> experience downtime for several hours on July 24th because a new version 
>> was rolled out that had an issue. It was a Friday, I was in an 
>> intercontinental flight without internet when the roll out happened and it 
>> was a small disaster. Google did take the issue seriously when I finally 
>> brought it to their attention but it took many hours to get back to stable 
>> ground. 
>>
>> I think Google can do some things to improve this. First, it needs to 
>> pass some control of when we upgrade the runtime to developers hands so the 
>> world does not change suddenly and unexpectedly under our feet. 
>> Furthermore, as they roll out new versions they should *automatically* 
>> revert applications back to the previous version if the error rate was 
>> almost zero before and spikes as soon as instances in the new version come 
>> onboard.
>>
>> I have filed this issue 
>>  in 
>> the public tracker. I highly encourage others to star it and add your ideas 
>> before you find yourselves in my or Julian’s shoes.
>>
>> Best 
>>
>>
>> On Sep 17, 2015, at 12:34 PM, Julian Bunn  wrote:
>>
>> We noticed on Sep 15 and 16 (a couple of days ago) that some of our GAE 
>> instances were running version 1.9.27 of the SDK, rather than the released 
>> version 1.9.26.
>>
>> (We coincidentally had several serious issues with our application.)
>>
>> Could someone please advise on how this can happen, and what we can do to 
>> prevent it happening in the future (i.e. force instances to only run the 
>> latest production release of the SDK)? Is there an application setting 
>> somewhere?
>>
>> I apologize if this is the wrong Group for such questions.
>>
>> Many thanks!
>> Julian
>>
>> -- 
>> 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/4ac6bcf5-9a32-40fe-ac5a-0886e4eceeb9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> PK
>> p...@gae123.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9efce746-8638-4201-a600-283eb4e83a0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Problem of "You do not have sufficient permissions to view this page"

[Jesse Scherer (Google Cloud Support)]

Hi all,

In order to help centralize communication I've created a "master" tracking 
issue: https://code.google.com/p/googleappengine/issues/detail?id=12242

I've asked Patrice to merge individual reports (there are about six at this 
point) into that issue once he's gotten all the information required. If 
you have filed a report you'll see it marked as duplicate. If you initially 
requested email, you will receive email updates from issue 12242 instead.

This is just to make sure you don't miss any updates, as eventually we'll 
have to let Patrice get some rest.

Thanks to everybody who has helped to pin this down.

On Monday, August 10, 2015 at 10:46:49 AM UTC-4, Patrice (Cloud Platform 
Support) wrote:
>
> Hi again,
>
> Just since I didn't include this in my previous reply and there are 
> concerns about this : if you do send me your HAR file, make sure you reply 
> privately to my message, so as not to make the file publicly available.
>
> From the arrow pointing down at the top right of my message, you can 
> choose "reply privately to owner". Please make sure to reply that way. I'll 
> still post the updates to the issue here, so that other people having the 
> same issue can see the resolution.
>
> Cheers
>
> On Monday, August 10, 2015 at 10:13:59 AM UTC-4, Patrice (Cloud Platform 
> Support) wrote:
>>
>> Hi to both of you,
>>
>> If one of you could reply on this thread attaching a HAR file of the 
>> failed attempt, it would help us figure out what could be the issue here. 
>> If you need help in capturing a HAR file, I would suggest this.  
>> 
>>
>> In the meantime, I've read that a customer who had the same issue as you 
>> managed to circumvent it by using the old console (appengine.google.com) 
>> instead of the newer one. This is not a fix, but it would let you work 
>> while we figure it out.
>>
>> Also, you could try disabling your add-ons and extensions, maybe one of 
>> them is interacting weirdly with the console or the requests and is causing 
>> issues.  
>> If
>>  
>> you find out this is the issue, please let me know which extension was the 
>> culprit.
>>
>> Cheers
>>
>> On Sunday, August 9, 2015 at 11:04:56 AM UTC-4, Benjamin C wrote:
>>>
>>> I have the exact same problem. I've tried creating projects, disabling 
>>> all APIs except for the one I want (Google Maps), and even joining the free 
>>> trial. I've had no problem with using Gmaps API before but that was quite 
>>> some time ago. Can someone help?
>>>
>>> On Sunday, August 9, 2015 at 1:04:30 AM UTC+8, yccheok wrote:

 Recently, I'm keep getting message of "You do not have sufficient 
 permissions to view this page", when I try to browse through "API & auth" 
 -> "Credentials"

 I'm the only owner of my Google App Engine account. Hence, I feel 
 strange of having such issues.

 Is there anything I can do, to avoid such problem?

 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d250a315-44ad-4fb1-bd6a-66b9e6ff6ad0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jesse Scherer (Google Cloud Support)]

Raul,

Thank you for taking the time to explain more. Your case has taken longer 
than we would hope, and while our lack of experience with circumstances in 
your country is an explanation, it is not an excuse for the trouble you 
have had. There is nothing you or we can do about these particular 
circumstances, but we can learn from your situation and hopefully do better 
in the future.

Apart from that, you make some good points about case handling in general. 
I will make sure our billing team is aware of your suggestions.

Regards,

On Monday, June 22, 2015 at 12:16:19 PM UTC-4, Raul Obagi wrote:
>
> Hi Jesse, thanks for answering, regarding my case, in fact there were many 
> answers as you highlight, my discontent took place when suddenly there was 
> an information vacuum that lasted about 2-3 days, likewise, this message 
> wrote before returning to resume contact and telephone call received from 
> Mr. Jorge, with respect to the opening of the second ticket I was forced to 
> do so due to the lack of answers because my situation is critical (and 
> still remains that have not revived the service).
>
> Then open the second ticket also experienced the same situation with Miss. 
> Nadaine and I repeat "this was again before resuming contact with mr. Jorge 
> and the phone call."
>
> So Jesse in this condition you describe you should take into account the 
> time which formalize my complaint and not now re-route the contact.
>
> The same sr. Jorge graciously understood me very well and very 
> sympathetically told me that my place had also made the same complaint.
>
> Yet mr. Jorge and I are working on solving the problem, we know what was 
> the reason for the suspension which had me very confused, sends several 
> identity verification and hopefully today or tomorrow at the latest all 
> this situation is resolved.
>
> I want you to know with all sincerity that is not my intention to 
> undermine the efficiency of its services, I consider myself a fan of its 
> technologies, and its mechanisms organized customer support, but I really 
> think that was a victim of a crack in their protocols, a situation with 
> which they are perhaps not used to dealing because here in Venezuela we 
> have exchange controls and for that reason my behavior was atypical to do 
> many repetitive attempts to pay with my credit card, I had the impression 
> of being relegated by ignorance or lack of experience with such 
> circumstances in my country.
>
> I want to reiterate my thanks to your services for me are the best tool on 
> the market and will remain so.
>
> Very grateful for your interest.
>
> El viernes, 19 de junio de 2015, 10:10:30 (UTC-4:30), Jesse Scherer 
> (Google Cloud Support) escribió:
>>
>> Hi Raul,
>>
>> I looked into the two billing cases which you referred to. I do see 
>> several messages from you and many responses from Jorge too. It looks like 
>> Jorge called you yesterday and that you discussed what information we need 
>> to further trouble-shoot.
>>
>> As she mentioned in your second case, the reason that Nadaine stopped 
>> replying is because she closed your second duplicate billing ticket. As she 
>> explained, Jorge was still working and it does not make sense to have two 
>> separate people working on your problem without coordinating. 
>>
>> Apart from your current issue, I want to address your fear that there is 
>> nobody to turn to. I hope that getting a call from Jorge today helps prove 
>> that every user can get billing and account help, and you don't need to pay 
>> $400 for Gold support in order to get help with your account. That level of 
>> support is intended for people who need to consult with us on application 
>> development and architecture. The technical support service guidelines 
>> <https://support.google.com/work/answer/6183505>explain this a lot more 
>> clearly than the main support page <https://cloud.google.com/support/>
>>  does.
>>
>> Regards,
>> Jesse
>>
>> On Thursday, June 18, 2015 at 11:20:09 AM UTC-4, Raul Obagi wrote:
>>>
>>> Hi Ryan and Dan in effect before writing here I had tried to contact 
>>> with Billing team support, I wanted to keep trying these days but i do not 
>>> receive any of any kind answer, I'm a little desperate because I have 6 
>>> days with this situation and they have not answered me, I had to open a 
>>> second ticket as the first left me talking to myself and turned out that 
>>> second ticket was worse, I have send around 17 messages imploring aid and 
>>> practically was alone in the desert, and worse not even achievement know 
>>> t

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

[Jesse Scherer (Google Cloud Support)]

Hi Raul,

I looked into the two billing cases which you referred to. I do see several 
messages from you and many responses from Jorge too. It looks like Jorge 
called you yesterday and that you discussed what information we need to 
further trouble-shoot.

As she mentioned in your second case, the reason that Nadaine stopped 
replying is because she closed your second duplicate billing ticket. As she 
explained, Jorge was still working and it does not make sense to have two 
separate people working on your problem without coordinating. 

Apart from your current issue, I want to address your fear that there is 
nobody to turn to. I hope that getting a call from Jorge today helps prove 
that every user can get billing and account help, and you don't need to pay 
$400 for Gold support in order to get help with your account. That level of 
support is intended for people who need to consult with us on application 
development and architecture. The technical support service guidelines 
explain this a lot more 
clearly than the main support page  does.

Regards,
Jesse

On Thursday, June 18, 2015 at 11:20:09 AM UTC-4, Raul Obagi wrote:
>
> Hi Ryan and Dan in effect before writing here I had tried to contact with 
> Billing team support, I wanted to keep trying these days but i do not 
> receive any of any kind answer, I'm a little desperate because I have 6 
> days with this situation and they have not answered me, I had to open a 
> second ticket as the first left me talking to myself and turned out that 
> second ticket was worse, I have send around 17 messages imploring aid and 
> practically was alone in the desert, and worse not even achievement know 
> the reason for the suspension.
>
> Two executives have assigned to me one for each ticket me and both the 
> executive "Jorge" as the executive "Nadaine" simply left the conversation.
>
> I fear that only seriously cater to customers platinium or gold, as they 
> require them to pay $ 400 monthly, and really seems unfair to have to pay 
> this much just to be heard.
>
> It's sad but true, no one to turn to.
>
> El sábado, 13 de junio de 2015, 14:14:47 (UTC-4:30), Raul Obagi escribió:
>>
>>
>> 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/b6d1fd6f-70c6-4f48-8e21-8da970f071b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: My Best App Engine Advice Would Be: Throttle Well

[Jesse Scherer (Google Cloud Support)]

Greetings Kaan,

You have brought up concerns in the past over how we handle this group, so 
I want to share some improvements with you and thank you for your part in 
inspiring them.

- In the interest of reducing confusion about where to post, we have 
updated our help center documentation 

 and welcome message 
 to better 
enumerate your community support options. Note also that pinned threads 
referring to StackOverflow have vanished.
- We've asked the support staff to change their display names on this forum 
to follow the pattern "Bob (Google Cloud Support)." This, hopefully, will 
make it more obvious when one of my colleagues' requests for information is 
motivated by Google's desire to provide support here.
- In order to prevent the appearance of censorship, I've asked the support 
staff to reserve the use of moderation powers for only the most extreme 
circumstances, such as when a certain Italian-speaking user shares his 
political opinions.
- Finally, in order to foster a sense of community we have re-organized how 
Support assigns itself to groups. You'll find that a few Support Team 
members  who 
have concentrated on this group are now nearly as active as yourself.

Regards,
Jesse

P.S. Another of my colleagues on the team will be following up on some 
specific points you made in part 2 of your mail.

On Tuesday, May 26, 2015 at 4:57:06 AM UTC-4, Kaan Soral wrote:
>
> I've been using App Engine for probably something like 5 years, I have one 
> major app that has been running for 5 years, it's very well polished, and 
> the traffic and behaviour of the app is very predictable *knocking on wood*
> I have another app that I've been working on for 3 years, it didn't take 
> off yet, the new app is unpredictable in behaviour, it's vast and 
> unthrottled
>
> While the old app has been handling millions of requests without errors 
> and issues, the new one is failing on even the simplest tasks, the logs are 
> filled with TransientError's, instance failures, transaction failures, the 
> whole thing is chaotic
>
> The old app has throttled queues and basic tasks, the throughput is well 
> calibrated to complete all the tasks in 5 hours, using optimal amount of 
> instances, the traffic is regular, it eases in and eases out throughout the 
> day (without throttling, the old app was in similar state before)
> The new app is built to perform, so it's queues have no limits, it trusts 
> App Engine to scale as much as it can
>
> Well turns out that trust isn't well placed, App Engine is supposed to 
> scale on it's own, yet when you leave the limits to the App Engine, it 
> fails to perform
> You might ask: "Why would I use App Engine if I'm going to manually scale 
> the limits myself?" - That's a good question, If you're going to have to 
> adjust the limits and throughput manually while your app grows, you might 
> as well use AWS or a similar more reliable service
>
> This is mostly a rant post, but the advice is still solid, one has to 
> manually calibrate the throughput of routines to prevent app spikes, the 
> instance births and deaths should always be eased in and eased out, 
> otherwise various services of app engine fail to perform
> On the bright side, throttling also reduces the costs significantly, so 
> it's a good idea to always keep an eye on the app and manually calibrate 
> all routines - on the other side, if your app gains additional traffic 
> without your supervision, these routines will hog and halt
>
> --
>
> On a more technical side, some of these errors are:
> "Request was aborted after waiting too long to attempt to service your 
> request." - they come in 100's - flood the logs - these are taskqueue 
> push tasks, so the error is pretty stupid, if they can't be handled, they 
> should be left in the queue
> "google.appengine.api.taskqueue.taskqueue.TransientError" - these are 
> from pull queues, there are invisible/untold limits of pull queues, this is 
> also very concerning, because if your app grows, your scale might be bound 
> by these limits, so try not to use pull queues too much
> "DeadlineExceededError's" - these are pretty random and rare, yet when 
> you run thousands of tasks, you get these in your logs, they might be 
> omitted
> Transactions errors and anomalies: these used to happen a lot, but I 
> switched to a pull queue based logic to prevent them, now they are replaced 
> by pull queue anomalies
>
> (It would have been great if limits and capacities of each service was 
> more transparent, and I really think taskqueues need some eased bucket 
> configurations, things that will help task batches to be executed in an 
> eased manner, currently the only way to achieve this is to put flat and low 
> throughput limits - similarly, same kind of control can be achi

[google-appengine] Re: Stack Overflow still official support channel?

[Jesse Scherer (Google Cloud Support)]

Jay, I apologize for the confusion around this. In this case the group is 
your best option. My colleague Ryan has followed up separately and should 
be able to help you out.

We have updated https://support.google.com/cloud/answer/3466163 to better 
explain community support options, and linked that page from the main Cloud 
Support page at https://cloud.google.com/support/

I've also updated the welcome message to include this information.

Regards,
Jesse

On Wednesday, May 13, 2015 at 7:46:49 PM UTC-4, Jay Kyburz wrote:
>
> I have an important question that has not been answered in over a week.
>
>
> http://stackoverflow.com/questions/30116388/switched-from-federated-login-back-to-google-accounts-api-nothing-but-errors
>
> Would be nice to have admin access to my own application again. 
>
> Jay.
>

-- 
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/00f0e5a4-4aee-4db1-99bd-7fc32337cc83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: official informations website

[Jesse Scherer (Google Cloud Support)]

Nick, great suggestion. It turns out there is such a page! It is this 
one: https://support.google.com/cloud/answer/3466163

You'll also find it linked from the main Cloud Support page 
at https://cloud.google.com/support/

I'm working on a welcome message which incorporates this information as 
well. I've probably missed some places in the GAE docs, but we are trying 
to be much more clear about this.

Regards,
Jesse

On Sunday, May 17, 2015 at 7:42:54 PM UTC-4, Nick wrote:
>
> This would make an excellent page on the GAE docs, especially if kept up 
> to date. 
>
> Also, there's a mailing list for production/live issues which is essential 
> for anyone deploying apps. 
>
> https://groups.google.com/forum/m/#!forum/google-appengine-downtime-notify

-- 
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/4f1694b0-d96a-4322-9b88-92efe8398be9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Channel API Hours Used" quota exceeded

[Jesse Scherer (Google Cloud Support)]

Hi PK,

The "Channel API Hours Used" quota has to with the TTL (time to live) of 
the channels you are opening. In Python, this is the "duration_minutes" 
variable, and it defaults to two hours: 
https://cloud.google.com/appengine/docs/python/channel/functions.

Note that enabling billing for your app increases the limit 15X to 180 
channel hours per minute. This would mean that every minute, you could open 
one channel with a TTL of 180 hours, ten channels with a TTL of 18 hours, 
1800 channels with 6 minute TTLs, and so on.

Beyond making sure that billing is enabled for your app, the best advice is 
to check that the TTL you are using makes sense. Again, this quota cares 
about how long of a TTL you ask for when you create the channel, not how 
long the channels eventually last. So, if in production you notice that 
channels only last a few minutes, lowering your TTL from the 2 hour default 
to 30 minutes would help a lot.

Regards, and let us know if you're still running into problems.

On Wednesday, May 6, 2015 at 12:21:21 AM UTC-4, PK wrote:
>
> For the first time ever today I get this message, in the console.
>
> The API channel.create_channel fails with an exception as a consequence.
>
> Has anybody experienced it? Is signing up for a support program the only 
> way to have it increased?
>
> Thanks,
> PK
> p...@gae123.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1fa8f7da-ef76-45af-bb69-0935e7cd2485%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: How to alleviate 200gb/day - 20$+ daily outgoing bandwidth image serving costs

[Jesse Scherer (Google Cloud Support)]

Some thoughts:

You could serve images from Cloud Datastore instead of from App Engine. You 
mention that bandwidth costs dominate instance time, but it should help a 
bit. If my math is correct, you're serving at least 250GB per day, so 
provided you're serving mostly to the US, the you'd get some volume 
discount now  and then a 33% 
discount once you top 10TB per month. If nothing else this would help you 
scale better.

You mentioned the images are served statically. If that's the case, can you 
crank up the expiration? What are you seeing which makes you suspect that 
your clients aren't cacheing properly? If your images periodically change 
can you just generate new filenames in conjunction with effectively 
infinite expiration time?

On Saturday, May 2, 2015 at 12:59:42 PM UTC-4, Kaan Soral wrote:
>
> Hi everyone
>
> I recently noticed a bump in costs after improving the static image 
> quality of my app, this bumped the daily bandwidth costs from ~7$'s to 
> 20$+'s
>
> Overall there are ~200 statically served images, I tried reducing the 
> quality of png's and turning them into jpg's, yet it degrades the image 
> quality, at the same level of quality, the size of the jpg's are identical 
> to the png's, so, as it is, paying the extra costs seem to be one option
>
> I'm also wondering whether there is an easier solution out there, maybe 
> using pagespeed as a CDN/cache with an easy config change, but as far as 
> I've researched, it didn't seem feasible/simple
>
> Setting up cloudflare for a subset of the traffic is another option, but 
> I'm not sure whether cloudflare can reliably serve all those images
>
> I checked some other CDN's / cloud solutions, they all seemed close to 
> AppEngine's pricing, CloudFront for example: 
> http://aws.amazon.com/cloudfront/pricing/ ~30% lower
>
> As it is, App Engine serves images well, yet the bandwidth costs are 
> higher than the instance hour costs, so I would like to reduce the 
> bandwidth cost if there is a simple solution out there that I'm missing
>
> (My default_expiration is "1h", I've also verified the "expires" header, 
> yet probably the consumer of the images doesn't cache them, I really wish 
> the issue was caching, but it doesn't seem the issue can be solved by 
> modifying the http caching)
>

-- 
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/228d7005-b6bc--b547-d86b141fbb4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: twitter API suddenly returning error 32 “Could not authenticate you.” only in prod GAE

[Jesse Scherer (Google Cloud Support)]

Hey guys, great sleuthing indeed!

I think this is related to another issue which was reported 
yesterday, https://code.google.com/p/googleappengine/issues/detail?id=11917

I'm going to add a summary of this thread to that issue, and I suggest you 
all "star" the issue, both to be copied on updates and questions from the 
engineers, and to underscore the impact of it.

On Friday, May 1, 2015 at 3:12:35 AM UTC-4, Ryan Barrett wrote:
>
> ...on an unrelated note, 1.9.20 was *way* better with utilization and 
> scheduling instances efficiently for my app. app engine team, i hope that 
> part survives!

-- 
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/23618afd-7622-4a54-9cf6-dfef3cc2dbb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jesse Scherer (Google Cloud Support)]

Hi,

I'm another one of the Support team members working on our community 
efforts. A lot of Karl's random thoughts and complaints ring true for me.

Right this minute, we're trying to sharpen the blunt instrument 

 
with which we send people to Stack Overflow. I think this will address some 
of the noise on this group and help new users get answers on Stack 
Exchange. Further out we're looking at a few ways to make Stack Exchange a more 
reliable place 

 
to get answers. 

I will follow up here in one week with a summary of what is going on with 
those Stack Exchange changes. I hope you'll keep the feedback coming until 
then.

Regards,
Jesse

On Monday, April 20, 2015 at 11:59:14 AM UTC-4, Brad Abrams wrote:
>
> Karl -- thanks for your feedback!  Rest assured we are absolutely 
> listening.  Responses to this thread have been forwarded to many different 
> teams within cloud and have caused lots of healthy discussion.  Your 
> feedback is greatly appreciated.  
>
> I will compile as many of the responses as I can and get back to this 
> group...  But please do keep the feedback coming!
>
>
> ..brad
>
> Brad Abrams
> Group Product Manager
> Google Cloud Platform
>   
>
> On Mon, Apr 20, 2015 at 8:44 AM, Karl MacMillan  wrote:
>
>>  Katie,
>>
>> I feel compelled to point out that how this discussion going is a good 
>> example of some of the things that I - and it seems others - are frustrated 
>> about. You’ve asked for and received concrete feedback. Yet we’ve received 
>> no answers or discussion back from Google engineers. At least a simple 
>> acknowledgement of the _specific_ issues we’ve raised from someone with 
>> some knowledge would be helpful. Otherwise how am I to know that you 
>> bringing the “feedback to the appropriate team members” is anything more 
>> than them receiving an email that they’ll simply delete?
>>
>> Look at this way - we’ve invested and in many cases bet our businesses on 
>> GCP. And especially with App Engine, this is very much an investment in an 
>> ecosystem that you’ve created that’s largely separate from the rest of the 
>> industry. It’s hard to have confidence in that bet given the almost total 
>> lack of public engagement from Google to help make this a vibrant ecosystem.
>>
>> Karl
>>
>>  
>>  On Apr 16, 2015, at 5:50 PM, Katie Ball (Google Cloud Support) <
>> kmrichard...@google.com> wrote:
>>
>> Hi Karl,
>>
>> You've taken some extra time and extra care to put this feedback together 
>> -- thank you! It's incredibly helpful; this is exactly what we need in 
>> order to better serve our users and the cloud computing community. 
>>
>> I've already taken your feedback to the appropriate team members to start 
>> improving things as suggested in your post.
>>
>> Is there anything that you are currently struggling with? If there is, 
>> we'd like to offer our help as a thank you.
>>
>> To our GCP community members: do you have any additional feedback you'd 
>> like to send our way? Any +1's to Karl's points? We'd love to hear from you!
>>
>> Thanks again,
>> 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/9bf4066c-1634-4d35-9b20-2e1f102b79e1%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/0935A678-ED9F-497C-8B4F-843643099447%40rakkoon.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 an

[google-appengine] Re: OAuth2 stopped working on all our apps

[Jesse Scherer (Google Cloud Support)]

Hello, please see https://status.cloud.google.com/incident/appengine/15006

You can also follow the App Engine Downtime Notify list 
(https://groups.google.com/forum/#!forum/google-appengine-downtime-notify) 
for ongoing details.

On Thursday, March 5, 2015 at 11:28:06 AM UTC-5, Daniel Florey wrote:
>
> What was that???
> Now they are all working again.
>
> On Thursday, March 5, 2015 at 4:19:05 PM UTC, Daniel Florey wrote:
>>
>> Since a few hours I'm getting weird responses when exchanging the OAuth2 
>> token.
>> Our apps are running on GAE/Java.
>> Anybody else?
>>
>>
>> Sorry... body { font-family: verdana, 
>> arial, sans-serif; background-color: #fff; color: #000; 
>> }> size=10>Go> face=times color=#f3c518 size=10>o> size=10>gl> face=times color=#c41200 size=10>e> style="border-bottom: 1px solid 
>> #dfdfdf;">Sorry...We're sorry.. but your computer or network may be 
>> sending automated queries. To protect our users, we can't process your 
>> request right now.See > href="https://support.google.com/websearch/answer/86640";>Google Help for 
>> more information.https://www.google.com";>Google 
>> Home
>>
>>

-- 
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/6d0e9170-d2f4-43d1-ae70-c8ea7c4c5ffe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jesse Scherer (Google Cloud Support)]

Hi Alejandro,

I wanted to speak to your point about the community on Stack Overflow. It's 
certainly the case that given the age of App Engine, many questions will be 
older. As to exactly how many questions get asked and whether there really 
has been a decline since 2013, your post made me very curious. So, I did a 
quick query of question volume using the Stack Exchange Data Explorer. You 
can see it alongside a graph of questions per month 
here: 
http://data.stackexchange.com/stackoverflow/query/279338/app-engine-questions-by-month#graph

Assuming my T-SQL is accurate, the past few months have been slower than 
the busiest months in 2014, but 500 new questions per month is still a lot.

It's also clear that all of those question don't do much good if nobody is 
answering them. We also noticed that there were quite a few unanswered 
questions about App Engine (and Google Cloud Platform in general) and so 
for the past few months, the support team has been reading and trying to 
answer literally *every* question which Stack Overflow considers 
"unanswered."

As one of the folks working full time to make forums like Stack Overflow 
and this group more useful to the community, I just wanted to assure you 
that these things are not in any way abandoned.

- Jesse

As somebody who is working full time to make public resources like Stack 
Overflow and this group more useful to our users, I just wanted to assure 
you that these forums are not by any stretch 

On Thursday, February 26, 2015 at 7:41:07 AM UTC-5, Alejandro Casanovas 
wrote:
>
> I will also want to make a claim for all those early users of App Engine 
> which are joining and trying to catch up the professional world using this 
> tool.
>
> It really seems abandoned to me. At least if you only (and I say here 
> ONLY) want to rely on PaaS and not going further.
>
> The majority of app engine questions in stackoverflow are from 2013 or 
> early and If you follow people who where actively contributing to app 
> engine on those days you find out they no longer answer nor they belong to 
> the app engine community any more. You really can't feel a big community of 
> people asking and getting involved in.
>
> It's also hard to find documentation on how to make a complete web app in 
> app engine. 
> For example, if you try to do it with Webapp2 framework (which I like the 
> most because of it's simplicity) you will find it really difficult to 
> implement oauth, sessions, rest, rbac, etc... 
> Webapp2 it's completely abandoned! And given that almost all app engine 
> examples on python rely on webapp2... that's a big flaw.
>
> I find out I need to move on managed VM's, because relying just on app 
> engine to make a complete web app It's impossible.
> It's really good to learn because you didn't need to think on server 
> issues, etc. But once you have the know-how... better move out.
>
> But I'm glad to see Google answering here and catching up with the long, 
> long, long.. issues list.
>
>
> On Thursday, 13 November 2014 01:44:38 UTC+1, Daniel Sturman wrote:
>>
>> Thanks for your candid responses. I hear your concerns loud and clear. I 
>> think the issues you raised all boil down to one thing: you’d like to see 
>> greater engagement between the App Engine team and our developer community.
>>
>> With regards to your specific concerns:
>>
>> I agree that an issue tracker is of little use if we aren’t actively 
>> triaging and updating it.  Although I could address the individual examples 
>> you pointed out one by one (e.g. we partnered with SendGrid to give you a 
>> good alternative for sending email), I think the proper action here is to 
>> triage the open issues in the tracker.  We have been ramping up support for 
>> doing this and you can expect to start seeing traction in the coming weeks. 
>>  
>>
>> As we ramp back up on feature work, we’ll also resume using the group for 
>> outbound communications regarding releases as well as any other 
>> developer-facing changes.  In parallel we’re having our support engineers 
>> monitor the group for issues and topics that need to be addressed by 
>> Google.  These will either be answered directly by that team or will be 
>> routed to the proper product management and / or engineering team. 
>>
>> -Dan
>>
>> VP, Engineering
>>
>>
>> On Wednesday, November 12, 2014 1:27:33 PM UTC-8, Marcel Manz wrote:
>>>
>>> Hey Daniel
>>>
>>> I'm very happy to hear back from Google on this forum and wish to point 
>>> out that it has to be very important for Google to follow this group in 
>>> order to share updates etc. Stackoverflow is an external site which is 
>>> great for code fragment sharing, but it's not a great place to discuss 
>>> about specific technology in general which should be discussed on a Google 
>>> hosted Group/Forum.
>>>
>>> If you would follow what the other large cloud provider is doing with 
>>> its forum you would immediately recognize the importance of having a 
>>> provider <> client