|Re: [google-appengine] 1.7.6 Pre-release SDKs Available||PK||3/13/13 9:57 AM|
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?
On Wednesday, March 13, 2013 at 7:50 AM, Janani Thanigachalam wrote:
|Re: 1.7.6 Pre-release SDKs Available||stevep||3/13/13 10:53 AM|
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:-)
|Re: [google-appengine] 1.7.6 Pre-release SDKs Available||Andrew Jessup||3/14/13 12:27 AM|
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.
|Re: 1.7.6 Pre-release SDKs Available||pdknsk||3/14/13 11:58 AM|
I tend to agree. The new server is a major improvement, but maybe not
ready for prime time just yet.
|Re: 1.7.6 Pre-release SDKs Available||takanao ENDOH||3/16/13 7:48 PM|
2013年3月13日水曜日 23時50分00秒 UTC+9 Janani Thanigachalam:
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".
|Re: [google-appengine] Re: 1.7.6 Pre-release SDKs Available||Amy Unruh||3/16/13 11:47 PM|
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?
|Re: [google-appengine] Re: 1.7.6 Pre-release SDKs Available||takanao ENDOH||3/17/13 6:24 PM|
I tried commands below:
> $ dev_appserver.py .
> $ 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.