For the record:
Google engineers did contact with me directly, and moved me back to
1.2.5. I was able to make some changes, and I'm assuming they made
some changes - and moved me back to 1.2.6 - the app seems to be OK
now.
Since I was complaining earlier, it seems only fair enough to give
credi
jacob-6 is currently on 1.2.5 but I'll be moving it to 1.2.6 later on
today now that we've fixed the underlying bugs in 1.2.5. Apologies
again for the confusion.
On Wed, Oct 14, 2009 at 10:21 AM, bvelasquez wrote:
>
> Just checking the status of this. My app was moved to the 1.2.5
> server yest
Just checking the status of this. My app was moved to the 1.2.5
server yesterday after this started happening. The 1.2.6 release is
out, so I'm wondering if my app (jacob-6) is on 1.2.6 or still on
1.2.5?
Barry
On Oct 13, 5:24 pm, RollingCircle wrote:
> At the moment, even a quick "Whoops - w
At the moment, even a quick "Whoops - we're on the case" sticky thread
on the forum from the Google team would be a comfort.
We've all had deployments which didn't go as smoothly as we'd hoped,
but when they don't, communication with affected parties is vital.
Otherwise, we're left to assume th
I would have to imagine, that Google intends to have a reliable
service here and that the release of 1.2.6 has been problematic. I
would like to push for a review of this release once it is finished.
There have been many problems caused to applications, that as you say
is completely unexpected and
Rodrigo,
Thanks for the response - I have replaced the module with one that
builds the tables dynamically -
But as we were discussing internally this morning: are we dealing with
a Tactical or a Strategic issue, here. The fact that we can have the
carpet pulled out from under us at any moment,
On Tue, Oct 13, 2009 at 1:56 PM, johnP wrote:
> OK, folks. Please let me know what to do in the contingency where I
> have an application that is functioning; have paying customers; then
> after a change on Google's side - it stops functioning; and when I try
> to contact people at Google, I get
OK, folks. Please let me know what to do in the contingency where I
have an application that is functioning; have paying customers; then
after a change on Google's side - it stops functioning; and when I try
to contact people at Google, I get radio silence?
johnP
On Oct 13, 8:19 am, johnP wr
Pickled KEY objects.
Any suggestions?
On Oct 13, 8:17 am, johnP wrote:
> This did not help. Many of my views reference a directory that
> contains a list of pickled objects.
>
> What should i do now...
>
> johnP
>
> On Oct 13, 7:45 am, Mahmoud wrote:
>
> > Yup. I found this out empirically y
This did not help. Many of my views reference a directory that
contains a list of pickled objects.
What should i do now...
johnP
On Oct 13, 7:45 am, Mahmoud wrote:
> Yup. I found this out empirically yesterday. Clearing memcache will
> solve it.
>
> On Oct 13, 10:42 am, "Nick Johnson (Goog
Yup. I found this out empirically yesterday. Clearing memcache will
solve it.
On Oct 13, 10:42 am, "Nick Johnson (Google)"
wrote:
> Hi johnP,
> The quick and easy solution is to clear your app's memcache.
>
> -Nick Johnson
>
>
>
>
>
> On Tue, Oct 13, 2009 at 3:36 PM, johnP wrote:
>
> > This bug
Hi johnP,
The quick and easy solution is to clear your app's memcache.
-Nick Johnson
On Tue, Oct 13, 2009 at 3:36 PM, johnP wrote:
>
> This bug is continuing in full-force for me this morning, and has
> taken my application offline.
>
> johnP
>
>
>
> On Oct 12, 4:19 pm, Taylor Hughes wrote:
>
This bug is continuing in full-force for me this morning, and has
taken my application offline.
johnP
On Oct 12, 4:19 pm, Taylor Hughes wrote:
> Thanks!
>
> On Oct 12, 4:10 pm, Jon McAlister wrote:
>
> > Moved dnzo.
>
> > On Mon, Oct 12, 2009 at 4:03 PM, Taylor Hughes wrote:
>
> > > My app
Thanks!
On Oct 12, 4:10 pm, Jon McAlister wrote:
> Moved dnzo.
>
>
>
> On Mon, Oct 12, 2009 at 4:03 PM, Taylor Hughes wrote:
>
> > My app is also affected; the app key is dnzo if you could also push me
> > back to 1.2.5 for now I'd appreciate it.
>
> > On Oct 12, 3:51 pm, Jon McAlister wrote:
Moved dnzo.
On Mon, Oct 12, 2009 at 4:03 PM, Taylor Hughes wrote:
>
> My app is also affected; the app key is dnzo if you could also push me
> back to 1.2.5 for now I'd appreciate it.
>
>
>
> On Oct 12, 3:51 pm, Jon McAlister wrote:
>> It's an issue in the 1.2.6 release we're pushing out to the
My app is also affected; the app key is dnzo if you could also push me
back to 1.2.5 for now I'd appreciate it.
On Oct 12, 3:51 pm, Jon McAlister wrote:
> It's an issue in the 1.2.6 release we're pushing out to the backends
> today. I've moved your app to a 1.2.5 appserver to temporarily fix i
It's an issue in the 1.2.6 release we're pushing out to the backends
today. I've moved your app to a 1.2.5 appserver to temporarily fix it.
And yes, we're working on a real fix too right now.
On Mon, Oct 12, 2009 at 3:48 PM, nasim wrote:
>
> I am getting this error in my app right now.
>
> Fi
17 matches
Mail list logo
