1.6.0 is now launched

[Gregory D'alesandre]

Hello All,

Just wanted to let you know that 1.6.0 is now live, information is posted here: http://googleappengine.blogspot.com/2011/11/app-engine-160-out-of-preview-release.html

Also, starting with 1.6.1 (our next release, NOT this release), URLFetch requests will honor the Accept-Encoding header. If your code sets this header then it must be prepared to receive content of the specified type. For more information please see: http://code.google.com/p/googleappengine/issues/detail?id=4978

Lastly, if you have any questions and would like to join us in a Hangout sign up at https://developers.google.com/events/ or, of course, respond to this message :)

Thank you!

Greg D'Alesandre

Senior Product Manager, Google App Engine

[pdknsk]

mini bug: extra <i> at http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes

[pdknsk]

Is there a summary of the TOS changes available? I accepted without
reading (as many probably have).

[Gregory D'alesandre]

There isn't a summary of changes as it was a complete re-write, that being said if you want to see the old terms you can find them here: http://code.google.com/appengine/terms_4.html

Thanks,

Greg

On Mon, Nov 7, 2011 at 1:31 PM, pdknsk <pdk...@googlemail.com> wrote:

Is there a summary of the TOS changes available? I accepted without
reading (as many probably have).

--
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-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Alexis]

I've got a small "issue" with this release:
the development server is writing many more entities to the local
datastore (log entries?).

As I have a hook on datastore write ops to log what is put and when,
it's polluting my logs but that's not the point:
My "issue" is that the local datastore file is getting bigger and
bigger while I run requests on my dev server.
Previously, this file size was stable. Now when I restart the dev
server, it takes much more time as it have to load a bigger datastore
file (several MB),
full of things I don't use.

Is there a way to prevent the dev server from adding these entities?
Thanks

[thstart]

Just installed  1.6.0 SDK

When running my app got the messages:

WARNING  2011-11-08 09:33:04,487 rdbms_mysqldb.py:90] The rdbms API is not available because the MySQLdb library could not be loaded.

Error: option --rdbms_sqlite_path not recognized

What is wrong?

[Amy Unruh]

On Wed, Nov 9, 2011 at 4:40 AM, thstart <ths...@gmail.com> wrote:

Just installed  1.6.0 SDK

When running my app got the messages:

WARNING  2011-11-08 09:33:04,487 rdbms_mysqldb.py:90] The rdbms API is not available because the MySQLdb library could not be loaded.

This is an ignorable warning-- it shouldn't cause you any problems. 

[Alfred Fuller]

Can you be more specific about what extra entities are actually being written. The SDKs now split batch get/delete/puts, are you sure you aren't just seeing that?

[PK]

Alfred/Alexis,

have you gotten anywhere with this issue? Is there a case opened?

I agree that what Alexis reports is indeed a very serious issue. Please take a look at issue 6355 for the way it manifests itself in my environment.

Thanks,
PK

[Alexis]

Alfred, I also noticed the split, but I'm talking about something
else.
What is being written are entities from inside the
google.appengine.api.logservice package
(_LogRecord, _LogLine, inside a namespace called "_Logs")

I suspect this may announce some feature about managing logs using
some APIs, which would be great,
but as this is not available yet and slows down performances of the
dev server as I described,
I just commented out any writes about these entities in the SDK
sources
(google.appengine.api.logservice.logservice_stub.py).

This "fixed" my issues.

On 19 nov, 04:08, PK <p...@gae123.com> wrote:
> Alfred/Alexis,
>
> have you gotten anywhere with this issue? Is there a case opened?
>
> I agree that what Alexis reports is indeed a very serious issue. Please

> take a look at issue 6355<http://code.google.com/p/googleappengine/issues/detail?id=6355>for the way it manifests itself in my environment.
>
> Thanks,
> PK