Re: [google-appengine] 1.7.6 Pre-release SDKs Available

[PK]

Having spent a lot of time with the new server but still using the old one, I want to say that the new app server is very promising but I personally think the decision to make the new app server the default now is a bit rushed. I hope you do not remove the old server before all our bugs have been addressed, this should be the criterion not the date. 

In the meantime, where are we supposed to file bugs now that the new server becomes the default so we can distinguish between the new and the old server issues, can somebody please clarify?

Thanks,

PK

http://www.gae123.com

On Wednesday, March 13, 2013 at 7:50 AM, Janani Thanigachalam wrote:

Hello Again Everyone!

We've posted the pre-release SDKs for Python and Java here:

http://code.google.com/p/googleappengine/downloads/list

Please see the pre-release notes below.

Regards,

Janani

App Engine Python SDK - Release Notes

Version 1.7.6

===============================

- The new and improved development appserver, which was previewed last release,

  now becomes the default. The old development appserver has been renamed to

  old_appserver.py and will remain available until the first release after

  1 July 2013 when it will be removed from the SDK.

- The XMPP API now has multi-JID get_presence. This provides the ability to get

  the availability of multiple users.

- Django 1.4 and Webob 1.2.3 are now promoted to GA.

- Apps now have the ability to fopen() files that are declared as static files

  in app.yaml using the application_readable flag.

- The dev_appserver now allocates automatic ids using the 'scattered' id

  allocation policy by default. For more information, please see "Specifying the

  Automatic ID Allocation Policy":

  https://developers.google.com/appengine/docs/python/tools/devserver#Using_the_

  Datastore

- New Search API quotas are now displayed in the Admin Console. These quotas are

  not currently enforced, but will be part of the pricing model for the Search

  API in a future release.

- The experimental Search API's ability to explicitly sort search results by

  SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order has

  been removed.

- Globally consistent indexes in the experimental Search API are now deprecated

  and will be removed in the next release.

- Task Queue tasks may now be added and deleted asynchronously. This allows

  applications to perform common task queue operations without blocking. This is

  an experimental feature.

- In the experimental MapReduce framework, shards that encounter Files API

  errors will retry three times before the entire job fails.

- ProtoRPC now supports deserializing and reserializing of unexpected fields.

- A new ProtoRPC field type for supporting datetime values has been added.

- Fixed an issue with the new dev_appserver failing on invalid login cookies. It

  now uses type="email" for email in the login form.

    https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?

    id=36

- Fixed an issue with the new dev_appserver to have fix_sys_path add the

  necessary libraries to sys.path making it now compatible with the testbed.

    https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?

    id=45

App Engine Java SDK - Release Notes

Version 1.7.6

=============

- The XMPP API now has multi-JID getPresence(). This provides the ability to get

  the availability of multiple users.

- The Java dev_appserver now allocates automatic ids using the 'scattered' id

  allocation policy by default. For more information, please see "Specifying the

  Automatic ID Allocation Policy":

  https://developers.google.com/appengine/docs/java/tools/devserver#Using_the_

  Datastore

- New Search API quotas are now displayed in the Admin Console. These quotas are

  not currently enforced, but will be part of the pricing model for the Search

  API in a future release.

- The experimental Search API's ability to explicitly sort search results by

  SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order has

  been removed.

- Globally consistent indexes in the experimental Search API are now deprecated

  and will be removed in the next release.

- Task Queue tasks may now be added and deleted asynchronously. This allows

  applications to perform common task queue operations without blocking. This is

  an experimental feature.

- Fixed an issue that caused NullPointerException in ListIndexesResponse

    http://code.google.com/p/googleappengine/issues/detail?id=8359

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

[stevep]

Janani wrote about the new GAE release: "Task Queue tasks may now be added and deleted asynchronously. This allows applications to perform common task queue operations without blocking. This is an experimental feature."

And just yesterday I started a thread complaining about the extreme variability of TQ additions API**. I will be on this like white on rice. Thanks G.

**recent log shows 1057 ms latency comprised of 0-cpu and 1057 api which was immediately preceded (within 2 seconds) by 0/47ms for the exact same handler function:-)

[Andrew Jessup]

Hi PK, we'll still be keeping the old Python dev_appserver in the SDK for another couple of releases to help people transition over. 

As for filing issues I'd suggest that any issues found in the SDK (be they in the old or new dev_appserver) be raised there, and if you are using the old dev_appserver, to note that fact in the bug report to help us track down the incident. If you find a bug in the open source project, then we will still be following that too and can respond to it there.

Andrew Jessup | Product Manager, Google App Engine

[pdknsk]

I tend to agree. The new server is a major improvement, but maybe not
ready for prime time just yet.

[takanao ENDOH]

Hi, Janani

2013年3月13日水曜日 23時50分00秒 UTC+9 Janani Thanigachalam:

- Fixed an issue with the new dev_appserver to have fix_sys_path add the

  necessary libraries to sys.path making it now compatible with the testbed.

    https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?

    id=45

That's great!

But I have a new problem on 1.7.6 pre-release.

I must be use `--address` option of dev_appserver.py for access from other devices.

Probably `--address` option was changing to `--host` on 1.7.6.

So I tried use `--host` option instead `--address` and then got errors bellow:

> google.appengine.tools.devappserver2.wsgi_server.BindError: Unable to bind 0.0.0.0:8081

Seems to have failed starting server "b1".

Thanks,

Takanao

[Amy Unruh]

hi Takano,

Yes, it is correct to now use '--host' (instead of '--address') with the new dev_appserver.

Re: your error, I am guessing you have a backends.yaml file, with a backend 'b1' defined?  

If you specify '--host 0.0.0.0', and use the default 8080 port, you should indeed see the first backend start up on http://0.0.0.0:8081, and so on.

This works fine in my tests.

Is it possible that your port 8081 was already in use at the time?

 -Amy

Thanks,

Takanao

[takanao ENDOH]

hi Amy,

Got it.

I tried commands below:

> $ dev_appserver.py .

It worked.

> $ dev_appserver.py --host 0.0.0.0 .

It's not worked.

> $ dev_appserver.py app.yaml

> $ dev_appserver.py --host 0.0.0.0 app.yaml

It's so good.

Thank you!

Takanao