[google-appengine] Re: Custom domain redirecting to appspot URL

[Sean Lynch]

The "Before you Begin" appears to no longer mention anything regarding the 
whitelisting requirement.  We attempted to migrate our site from GoDaddy to 
App Engine but had to abort due to the redirect issue.  Where is best place 
to subscribe to know when this has been resolved.  This thread?


On Tuesday, January 31, 2017 at 5:54:03 PM UTC-5, Alex (Cloud Platform 
Support) wrote:
>
> Hi Himanshu,
>
> As your application is hosted on a GAE Flexible environment instance 
> (since redirected URL includes *.appspot-preview.com), custom domains 
> need to be whitelisted as mentioned in this Before you Begin section 
> .
>  
> In the third point, it is possible to whitelist the domains by filling out 
> this Google contact form 
> . 
> However, as this form is currently unavailable, you will be contacted by 
> email shortly to provide additional information regarding your project.
>

-- 
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/bfed6e96-aef4-4162-96bc-19ea8a0744fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Deleted default Google Cloud Storage bucket, unable to recreate

[Sean Lynch]

While attempting to get the ACL setup correctly on the default Google Cloud 
Storage bucket (APPID.appspot.com), I deleted this default bucket but now I 
see no way to recreate it.  

Under Cloud Integration on the old App Engine console, I now see The 
project was created successfully. See the Basics section for more details. 
instead of the create button.  At the top of Application Settings I see Google 
Cloud Storage Bucket: APPID.appspot.com but clicking the link returns A 
required resource is not available.

I tried to manually recreate the GCS bucket under the new Cloud console, 
but get the error:

 Note that a bucket name may only contain a dot if it is a valid domain 
 name, such as example.com or sub.example.com. You will need to 
 demonstrate that you are an owner or manager of this domain before creating 
 the bucket.


I'd rather not create a new application to replace this one.  How can I 
recreate the default bucket? 

-- 
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/36dacd1f-faba-48ca-9fd6-e489f3980a9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Deleted default Google Cloud Storage bucket, unable to recreate

[Sean Lynch]

While GCS is very cheap, the default bucket is free up to 5GB and more
importantly, does not require billing to be enabled. I just ported an
application using the deprecated google.appengine.ext.files API to GCS but
now I'll need to enable billing to restore this file upload functionality
for their application.

On Mon, Jun 8, 2015, 6:20 PM Jeff Schnitzer j...@infohazard.org wrote:

 While I haven't made this particular mistake, it's actually kind of a big
 deal. We deploy the same code to acceptance, staging, etc environments.
 Using the default bucket means we don't have to set up buckets by hand for
 each of those environments. Before you say that's not a big deal, the
 entire career of devops exists because there are a thousand no big deals
 required to set up and run environments. GAE's primary value proposition is
 no devops.

 Also, it's just very bad practice to have buttons that, when accidentally
 clicked, wedge the application into a state that cannot be recovered
 without spending engineering resources on changing the deployment process.

 I would star this issue.

 Jeff

 On Mon, Jun 8, 2015 at 2:38 PM, Patrice (Cloud Platform Support) 
 pvoutsi...@google.com wrote:

 Hi Sean,

 Unfortunately, no there is no way to re-create the default bucket if you
 deleted it.

 I don't see why you really need the default one though... can't you use
 any other bucket, since they have the exact same behavior as the default
 ones?

 If you really need to use the default one, yes unfortunately the only way
 to do so is to re-create a new app, but again, I don't see why you need to
 take the default one, when you can just create a new one.

 Cheers!


 On Monday, June 8, 2015 at 4:00:39 PM UTC-4, Sean Lynch wrote:

 While attempting to get the ACL setup correctly on the default Google
 Cloud Storage bucket (APPID.appspot.com), I deleted this default bucket
 but now I see no way to recreate it.

 Under Cloud Integration on the old App Engine console, I now see The
 project was created successfully. See the Basics section for more details.
 instead of the create button.  At the top of Application Settings I see 
 Google
 Cloud Storage Bucket: APPID.appspot.com but clicking the link returns
 A required resource is not available.

 I tried to manually recreate the GCS bucket under the new Cloud console,
 but get the error:

 Note that a bucket name may only contain a dot if it is a valid domain
 name, such as example.com or sub.example.com. You will need to
 demonstrate that you are an owner or manager of this domain before creating
 the bucket.


 I'd rather not create a new application to replace this one.  How can I
 recreate the default bucket?

  --
 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/4c503d36-706c-4cbe-ba70-984b529c856f%40googlegroups.com
 https://groups.google.com/d/msgid/google-appengine/4c503d36-706c-4cbe-ba70-984b529c856f%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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/Bq9TeY1f3kM/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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-appengine/CADK-0ujy7aWjwjPwC%3DY6-QJRodcDfZBcnG23%3D%2Briq8n2NsRRpw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-appengine/CADK-0ujy7aWjwjPwC%3DY6-QJRodcDfZBcnG23%3D%2Briq8n2NsRRpw%40mail.gmail.com?utm_medium=emailutm_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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAAEs42-hpnpnMdvxB4E3ea40FK%2BQ1cUfn69%2BYM9Lc%3DDHZud5tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Blobstore and New Billing

[Sean Lynch]

I was just thinking about this the other day, and am also interested on how 
the transitionwill affect the Blobstore API availability.

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/869o6VPePtMJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Blobstore and New Billing

[Sean Lynch]

Thanks

On Sat, Sep 3, 2011 at 12:30 AM, Gregory D'alesandre gr...@google.comwrote:

 We will enable blobstore on free apps ahead of time so you won't have to
 time this too precisely.  We'll announce once this is live.

 Greg


 On Fri, Sep 2, 2011 at 6:27 AM, Sean Lynch techni...@gmail.com wrote:

 I was just thinking about this the other day, and am also interested on
 how the transitionwill affect the Blobstore API availability.

 --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To view this discussion on the web visit
 https://groups.google.com/d/msg/google-appengine/-/869o6VPePtMJ.

 To post to this group, send email to google-appengine@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.


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


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

[google-appengine] Blobstore and New Billing

[Sean Lynch]

Does the Blobstore API still require billing to be enabled to be used? 
 Based on the quota docs, it does:
http://code.google.com/appengine/docs/quotas.html#Blobstore

But there is no mention of it on the Blobstore pages:
http://code.google.com/appengine/docs/python/blobstore/overview.html

Also, I saw mention that the Blobstore will be free (up to 5G) under the new 
billing model.  When will this take effect?
https://groups.google.com/forum/#!msg/google-appengine/VCYbRH4WWBI/mQKSo1tRzfEJ

I'm currently working on a new Google Apps / App Engine site for a customer, 
and needed to notify them whether they needed to enable billing (it's low 
traffic, and thus hadn't planned on it up to this point).

Thanks,
Sean

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/CrxFAAHjoFkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Blobstore and New Billing

[Sean Lynch]

Thanks for the reply.

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Jy1UVXGHi8IJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Post-mortem for March 8th, 2011 outage

[Sean Lynch (Google)]

This document is the post mortem describing the March 8th 2011 App
Engine outage.

Summary

On March 8th 2011, a subset of Python App Engine applications using
the Master/Slave Datastore configuration were affected by a service
outage that lasted, in the worst case, up to five and a half hours.
During the outage, a percentage of requests to affected applications
would fail with errors when traffic was routed to affected instances;
application logs would have shown affected instances were unable to
import standard Python modules. The outage was caused by a previous
update to the system, which made it impossible to cleanly perform
future system updates without disruption.

Root Cause

In the morning of March 8th, the App Engine team pushed a new version
of the App Engine Python runtime. While the new Python runtime
contained no known issues, a performance optimization in a system
update pushed on March 3rd included a bug which would cause future
updates to App Engine runtimes to disrupt running applications as the
new runtime rolled out. Once the bug was triggered, applications would
be unable to import requested Python modules.

Timeline

March 3rd 2011 - A new runtime is pushed to production, uneventfully.
A configuration change made in this runtime contains a bug which will
disrupt future rollouts of new runtimes.

March 7th 2011 - 8:00 PM US/Pacific - Release of a new Python runtime
rolls out to the internal instance of App Engine, which is only used
to test new App Engine releases, and only contains internal Google
applications.

March 8th 2011 - 2:35 AM US/Pacific - Release of the new Python
runtime begins to rollout to production, first to the Master/Slave
Datastore applications. It is expected that this push is safe, as
nothing adverse was observed in the rollout to the internal instance
of App Engine. The push installs the new Python runtime, which due to
the bug present in the previous release, immediately disrupts the
running applications.

March 8th 2011 - 2:50 AM US/Pacific - A measurable rise in user
visible error rates across the service is noted. Investigation begins.

March 8th 2011 - 3:30 AM US/Pacific - Rollout of the update to
production is stopped. It had only reached 15% of the Python Master/
Slave Datastore service in production.

March 8th 2011 - 3:45 AM US/Pacific - The root cause of the problem is
identified, and the remediation method is determined: all of the
infrastructure underlying the Python Master/Slave Datastore
applications must be restarted. A hard restart of the underlying
infrastructure would fix the problem instantly, but would also disrupt
the entire Python Master/Slave Datastore population for tens of
minutes. As only a subset of the Python Master/Slave Datastore
applications are affected, monitoring analysis is used to find the
worst-affected infrastructure, which is restarted in small batches so
as not to disrupt the other, healthily-serving applications.

Mar 8 2011 - 5:20 AM US/Pacific - Enough infrastructure has been
restarted that the user-visible outage is largely over at this point.
A verification rollback begins, where the entire Python Master/Slave
Datastore infrastructure is restarted in the background at
conservative speed, to ensure that the problem is remediated globally.

Mar 8 2011 - 8:05 AM US/Pacific - A subset of Python Master/Slave
Datastore applications are determined to still be affected, and the
relevant infrastructure is manually restarted. The user-visible outage
is completely over at this point.

March 8th 2011 - 10:00 AM US/Pacific - Verification rollback complete.

Issues and Fixes

- The configuration bug in the March 3rd 2011 push was missed during
design  review.

- The impact of the configuration bug introduced on the March 3rd 2011
push was subtle and only manifested slowly in a subset of applications
as they restarted. This resulted in a new failure mode that automated
systems were not configured to detect. While it manifested in the push
to the internal instance, it appeared too slowly to inform us there
was a bug, and that we should not have continued with the push to
production.
   - Implement monitoring and alerting on additional aspects of the
health of the runtimes, especially during updates. Gate releases to
production on successful verification of runtime health in the
internal instance.

- The Status Site did not indicate errors during the outage. The
disruption only manifested as application instances restarted (or did
late imports of modules). As the applications probed by the Status
Site had not restarted, they were not disrupted.
   - Incorporate data from a subset of production applications into
the display on the status site, not just monitoring data.

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.

[appengine-java] Re: Urgent: GAE app is incredibly slow!

[Sean Lynch (Google)]

We've acknowledged the issue and are working on fix that should be out early 
this week. To track the bug, please see:
http://code.google.com/p/googleappengine/issues/detail?id=4544

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: A serious problem was encountered (Error code 203)

[Sean Lynch (Google)]

We've acknowledged the issue and are working on fix that should be out
early this week. To track the bug, please see:
http://code.google.com/p/googleappengine/issues/detail?id=4544

On Feb 18, 2:48 am, Ian Marshall ianmarshall...@gmail.com wrote:
 Hi Didier,

 I know that I am not Luis but I too got these error messages. The
 second post of the above entry did not address my problem.

 I have just made an entry to googleappengine Issue 4544 (all requests
 fail with error code 203) at

 http://code.google.com/p/googleappengine/issues/detail?id=4544q=%22E...

 to describe more fully what I am getting and when.

 Strangely, after a few hours the errors seem to have gone away - for
 now.

 Ian

 On Jan 20, 5:10 am, Didier Durand durand.did...@gmail.com wrote:







  Hi,

  You probably have response to your question in the second post of this
  thread:http://groups.google.com/group/google-appengine-java/browse_thread/th...

  Let us know if it solved your issue

  regards

  didier

  On Jan 19, 8:37 pm, Luis l.pereira.fernan...@gmail.com wrote:

   Hi all,

   A couple of days ago I deployed a new cron tast that works fine on dev but
   in the app engine it has never worked. I always get theerrorbelow
   (although it is actually logged as a warning), without any further
   information about what it is really going wrong.

   Could someone from the App Engine team help me with this?

   Many thanks,
   Luis

   01-19 08:39AM 43.505 /cron/generalmaintenance 500 610280ms 7781cpu_ms
   571api_cpu_ms 0kb AppEngine-Google; (+http://code.google.com/appengine)
   See details
   0.1.0.1 - - [19/Jan/2011:08:49:53 -0800] GET /cron/generalmaintenance
   HTTP/1.1 500 0 - AppEngine-Google; (+http://code.google.com/appengine)
   my-test-app01.appspot.com ms=610281 cpu_ms=7782 api_cpu_ms=572
   cpm_usd=0.216186 queue_name=__cron
   task_name=545f09d3b090cee12a3e589deeb3d83b pending_ms=206 exit_code=203W
   01-19 08:49AM 53.768 A serious 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. If you see 
   this
   message frequently, you should contact the App Engine team. (Errorcode203)

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine for Java group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[google-appengine] Re: Deadline errors better today, Wed Nov 3rd, but still happening

[Sean Lynch (Google)]

What is your Application ID?

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

[google-appengine] Re: Tons of DeadlineExceededExceptions recently

[Sean Lynch (Google)]

What is your application ID?

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

[google-appengine] Re: Tons of DeadlineExceededExceptions recently

[Sean Lynch (Google)]

Yes, we are tracking an ongoing datastore latency issue. You can follow
our progress here:

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

[google-appengine] Re: Tons of DeadlineExceededExceptions recently

[Sean Lynch (Google)]

Actually posting link this time:
https://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/f0857aa4aa10852f?hl=en

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

Re: [google-appengine] Unable to Access Dashboard or Logs

[Sean Lynch (Google)]

Admin Console accessibility issues were related to this problem:
https://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/f0857aa4aa10852f



They should be resolved now so please let me know if you are still
seeing problems.

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

[google-appengine] Re: Twitter issues

[Sean Lynch (Google)]

Things should be working properly now.

On Sep 28, 12:36 pm, nischalshetty nischalshett...@gmail.com wrote:
 Keeping fingers crossed, hope this gets sorted out soon.

 -Nischal

 On Sep 28, 6:46 am, Ikai Lan (Google) ikai.l+gro...@google.com
 wrote:



  Hey everybody,

  We're currently being blocked by Twitter. We're reaching out right now to
  the Twitter team to resolve the issues.

  --
  Ikai Lan
  Developer Programs Engineer, Google App Engine
  Blogger:http://googleappengine.blogspot.com
  Reddit:http://www.reddit.com/r/appengine
  Twitter:http://twitter.com/app_engine

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

[google-appengine] Re: Issue with precompilation-enabled java sdk 1.3.5

[Sean Lynch]

Yes, it is now on by default (I will correct the documentation).

We are investigating deployment issues that's come up for Python
developers which may also be related to precompilation.

On Jul 19, 11:41 pm, Galoch galoch...@gmail.com wrote:
 Hi,

 I looked at the release notes of 1.3.1 where it says Java
 Precompilation is now on by default where as the current
 documentation at link [http://code.google.com/appengine/kb/java.html]
 says it will be supported in future versions.

 I believe, former is true. Reason being, I am unable to deploy
 application with default settings in my appengine-web.xml since
 deployment fails with 500 internal server error. Has anyone else
 noticed it. I have seen this issue pop up after I started using task
 queues.
 After explicitly turning off precompilation of JSPs, I am able to
 deploy but I am not sure what would be the impact on overall app
 performance.

 Thanks
 G

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

[google-appengine] Re: Server Error on code upload

[Sean Lynch]

We're looking into it.  Can you try deploying your applications
without the python_precompiled flag in app.yaml?

On Jul 20, 9:29 am, José Moreira matrixowns...@gmail.com wrote:
 I also been having this problem ocasionally, my guess is appengine overload

 2010/7/20 vivpuri v...@vivekpuri.com

  I have been getting server error while trying to upload code to prod
  since 8 AM EST. Anyone else facing this issue? I do have the
  derived_file_type: - python_precompiled set in the app.yaml.

  --
  You received this message because you are subscribed to the Google Groups
  Google App Engine group.
  To post to this group, send email to google-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

 --
 irc://josemore...@irc.freenode.nethttp://pt.linkedin.com/in/josemoreirahttp://djangopeople.net/josemoreira

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

[google-appengine] Re: Scheduled Maintenance?

[Sean Lynch (Google)]

Yep sorry for the delay.  Keep any eye on the eye on the thread
vivpuri linked to, we will update that thread when the read-only
period has finished.

On Feb 17, 5:46 pm, Greg g.fawc...@gmail.com wrote:
 Oooops... there it goes. Maybe my message reminded them!

 On Feb 18, 2:37 pm, Greg g.fawc...@gmail.com wrote:

  Have I got my timezones wrong, or is the scheduled maintenance not
  happening? According to my calculations it should have started half an
  hour ago...

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