RE: [google-appengine] Re: __setattr__ and __getattr__ causing memcacahe error in 1.8.5

2013-09-30 Thread Brian Becker 
Yes.
 def __setattr__( self, name, value ):
   if name == 'orig':
# force value to string & kill whitespace
value = unicode(value).strip()

## Lots more cleaning is necessary
# clean off ending characters
value = value.rstrip(' ,;:)(')
# Ps 3:1; cf. => Ps 3:1
if value[-3:] == 'and': value = value.replace('and','')
if value[-2:] == 'cf': value = value.replace('cf','')
# clean off ending characters again
value = value.rstrip(' ,;:)(')
self.__dict__[ 'orig'] = value

From: google-appengine@googlegroups.com 
[mailto:google-appengine@googlegroups.com] On Behalf Of timh
Sent: Tuesday, October 01, 2013 12:34 AM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Re: __setattr__ and __getattr__ causing memcacahe 
error in 1.8.5

You should show some code.  Are you actually overriding __settattr__ and 
__getattr__ in your models ?

T

On Tuesday, October 1, 2013 12:34:12 PM UTC+8, Brian Becker wrote:
After upgrading to 1.8.5 (from 1.8.1) I instantly had Internal Server Error 
whenever my class was instantiated and placed in memcache:
  daRef = oRefFinder()
  memcache.set( 'theRef', daRef)

The last lines of the error trace says that the memcache.set command:

  File "/base/data/home/apps/s~refindservice/1.370602298270267557/main.py", 
line 117, in get

memcache.set('theRef' , daRef )

  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 763, in set

namespace=namespace)

  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 868, in _set_with_policy

time, '', namespace)

  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 947, in _set_multi_async_with_policy

stored_value, flags = _validate_encode_value(value, self._do_pickle)

  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 227, in _validate_encode_value

stored_value = do_pickle(value)

  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 392, in _do_pickle

pickler.dump(value)

TypeError: 'NoneType' object is not callable


I finally traced it to __setattr__ and __getattr__. If I go into my class and 
change  __setattr__ and __getattr__ methods to something else like tabooset and 
tabooget -- Memcache error goes away. G.

If I delete all the content in my __setattr__ and just put "pass" -- it still 
bombs -- so this is specific to the name of those methods.

First, what is going on?
Second, is there some other way I'm supposed to be setting and getting 
attributes in my classes in GAE?

And yes, this was operating fine before I upgraded from 1.8.1 to 1.8.5.

Brian

--
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/2d9UO1m0wV8/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.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: __setattr__ and __getattr__ causing memcacahe error in 1.8.5

2013-09-30 Thread timh 
You should show some code.  Are you actually overriding __settattr__ and 
__getattr__ in your models ?

T

On Tuesday, October 1, 2013 12:34:12 PM UTC+8, Brian Becker wrote:
>
> After upgrading to 1.8.5 (from 1.8.1) I instantly had Internal Server 
> Error whenever my class was instantiated and placed in memcache:
>   daRef = oRefFinder()
>   memcache.set( 'theRef', daRef)
>
> The last lines of the error trace says that the memcache.set command:
>
>   File "/base/data/home/apps/s~refindservice/1.370602298270267557/main.py", 
> line 117, in get
> memcache.set('theRef' , daRef )
>   File 
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
>  line 763, in set
> namespace=namespace)
>   File 
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
>  line 868, in _set_with_policy
> time, '', namespace)
>   File 
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
>  line 947, in _set_multi_async_with_policy
> stored_value, flags = _validate_encode_value(value, self._do_pickle)
>   File 
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
>  line 227, in _validate_encode_value
> stored_value = do_pickle(value)
>   File 
> "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
>  line 392, in _do_pickle
> pickler.dump(value)
> TypeError: 'NoneType' object is not callable
>
>
>
> I finally traced it to __setattr__ and __getattr__. If I go into my class 
> and change  __setattr__ and __getattr__ methods to something else like 
> tabooset and tabooget -- Memcache error goes away. G.
>
> If I delete all the content in my __setattr__ and just put "pass" -- it 
> still bombs -- so this is specific to the name of those methods.
>
> First, what is going on? 
> Second, is there some other way I'm supposed to be setting and getting 
> attributes in my classes in GAE?
>
> And yes, this was operating fine before I upgraded from 1.8.1 to 1.8.5.
>
> Brian
>  
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] __setattr__ and __getattr__ causing memcacahe error in 1.8.5

2013-09-30 Thread Brian Becker 
After upgrading to 1.8.5 (from 1.8.1) I instantly had Internal Server Error 
whenever my class was instantiated and placed in memcache:
  daRef = oRefFinder()
  memcache.set( 'theRef', daRef)

The last lines of the error trace says that the memcache.set command:

  File "/base/data/home/apps/s~refindservice/1.370602298270267557/main.py", 
line 117, in get
memcache.set('theRef' , daRef )
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 763, in set
namespace=namespace)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 868, in _set_with_policy
time, '', namespace)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 947, in _set_multi_async_with_policy
stored_value, flags = _validate_encode_value(value, self._do_pickle)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 227, in _validate_encode_value
stored_value = do_pickle(value)
  File 
"/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/api/memcache/__init__.py",
 line 392, in _do_pickle
pickler.dump(value)
TypeError: 'NoneType' object is not callable



I finally traced it to __setattr__ and __getattr__. If I go into my class 
and change  __setattr__ and __getattr__ methods to something else like 
tabooset and tabooget -- Memcache error goes away. G.

If I delete all the content in my __setattr__ and just put "pass" -- it 
still bombs -- so this is specific to the name of those methods.

First, what is going on? 
Second, is there some other way I'm supposed to be setting and getting 
attributes in my classes in GAE?

And yes, this was operating fine before I upgraded from 1.8.1 to 1.8.5.

Brian
 

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

2013-09-30 Thread Doug Anderson 
FWIW... I'd like to add my voice in support of a high priority for this 
capability.  Now that we have SSL... improved domain management is at the 
top of my wish list.  On the email front... I use Mailgun with App Engine 
precisely because I need more flexibility than GAE's native email provides. 
 On the receiving end Mailgun can forward to an HTTP POST handler in your 
GAE app similar to the native GAE email.  I'm not sure if Sendgrid has the 
same HTTP POST capability for incoming mail.   

On Sunday, September 29, 2013 9:42:33 PM UTC-4, Lawrence Mok wrote:
>
> I got exactly the same as yours, that's so inconvenient especially for a 
> company who own 20+ websites for different products.  
>
> On Wednesday, September 4, 2013 3:37:29 PM UTC+8, Sandeep wrote:
>>
>>
>>> Even the use of sub organization is banned now. We don't need new mail 
>>> google apps accounts. We just want to launch it as a sub organization, so 
>>> the site is Up. I wonder even that is not allowed now. 
>>>
>>> And this is the same process I did for many domains of many clients 
>>> earlier wn we have apps for free.
>>>
>>>
>>> 
>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: SDK1.8.4 did break cloud enpoint generation

2013-09-30 Thread Johan Compagner 
now that 1.8.5 is out i throught lets try it again
But at first the same problem again.

But then i rechecked what GPE i had installed and yes it was 3.3.x 
Check for updates didn't really update that, but then i did go through -> 
install new software
with the 4.3 url (that i already was using for a long time) and there i did 
see the 3.4.x version 
When i selected that to install, Eclipse said at first that it can't really 
install it because of conflicts, but after while eclipse came to the 
conclusion that it could uninstall 3.3 and install 3.4 
After that was being installed and after a restart it seemed to work fine.

But the problem is that 3.3 is not updated somehow to 3.4 (i did get 
updates but i guess not really 3.4)
So this could be a problem of many others also, which are coming from an 
older install and are constantly just upgrading..


On Saturday, September 7, 2013 7:36:49 PM UTC+2, Ludovic Champenois wrote:
>
> Which version of the GPE plugin itself are you using? Verify it is the 
> latest: GPE 3.4.0
>
>
> On Saturday, September 7, 2013 2:20:55 AM UTC-7, Johan Compagner wrote:
>>
>> I updated through eclipse to the 1.8.4 release, but then i tried to do 
>> the endpoint generation it failed with this exception:
>>
>> java.lang.NoSuchMethodException: 
>> com.google.api.server.spi.tools.CloudClientLibGenerator.generateClientLib(java.lang.String,
>>  
>> com.google.api.server.spi.tools.ClientLibGenerator$Language, 
>> java.lang.String, java.io.File)
>> at java.lang.Class.getMethod(Class.java:1655)
>> at 
>> com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createClientLibFromApiConfig(SwarmApiCreator.java:101)
>> at 
>> com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createSwarmApi(SwarmApiCreator.java:212)
>> at 
>> com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmServiceCreator.create(SwarmServiceCreator.java:475)
>> at 
>> com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction$1.run(GenerateSwarmApiAction.java:84)
>> at 
>> org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
>> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
>> at 
>> org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
>> at 
>> com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction.run(GenerateSwarmApiAction.java:80)
>> at 
>> org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
>> at 
>> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
>> at 
>> org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
>> at 
>> org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
>> at 
>> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
>> at 
>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>> at 
>> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
>> at 
>> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
>> at 
>> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>> at 
>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
>> at 
>> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
>> at 
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>> at 
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
>> at 
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
>> at 
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
>> at 
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
>> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
>>
>>
>> i quickly reverted to 1.8.3 and that wor

[google-appengine] get_serving_url is BROKEN with App Engine 1.8.5!

2013-09-30 Thread John Wheeler 
Google, Please take a look at these image URLs: You will notice that they 
do not respect the s resize parameter past their original sizes:

https://lh6.ggpht.com/iPsqjK1C0cqxj_ENLm-9nbMmWrpwiNfy_bOV6KMZ5PGQwPhZ3PVrT4lgL1lPODrufS0aKFyzXoQjrC_goWRCllJUJA=s1000
 
is 738px x 326px (original size)

https://lh4.ggpht.com/ObJBaDz0LRmQd2vr5sgWcwyO89imLhEGK8b-j_Qq6jwZgg8foS5oVXt4SjNQG-qxmZ8gbKSawTgDQBXEwEd30UfC4I8=s1000
 
is 851px x 315px (original size)

As far as I know, this was not the case before 1.8.5 rollout. 

John

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] manually Write a http soap request

2013-09-30 Thread giuseppe giorgio 
could someone help me with my problem? thanks in advice

http://stackoverflow.com/questions/19099044/manually-build-soap-service-request

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Concurrency broken?

2013-09-30 Thread Jeff Schnitzer 
One day after I posted that message, behavior returned to normal and GAE
became fast again. AFAICT, it's been fine since.

Jeff


On Mon, Sep 30, 2013 at 2:13 AM, Nicolas Fonrose (Teevity) <
nicolas.fonr...@teevity.com> wrote:

> Hi Jeff,
>
> For the last three weeks, we are seeing quite the opposite of what you
> describe here ! This is a very good surprise to us because we are usually
> facing the problem you describe (many instances being started for no
> apparent reasons).
>
> Over these three weeks, our app has literaly been flying, not sending any
> user facing requests to starting instances. The number of instances started
> hasn't really reduced compared to the previous month, but 98% of them are
> sent to already running so our users don't experience high latency.
>
> We haven't got any hard facts to draw conclusion on why this has changed,
> but we've got the feeling that this might be due to an external system we
> have recently added (not running on AppEngine) and that sends regular
> requests to our app (several requests per minutes), thus generating not
> high but very regular traffic to the app.
>
> If this can help other AppEngine/Java users solve the well known
> "high-latency on user facing requets" issue ...
>
> Nicolas
>
>
> On Saturday, September 21, 2013 11:29:04 PM UTC+2, Jeff Schnitzer wrote:
>>
>> Yesterday and today (and possibly longer) our (Java) app is spinning up
>> quite a few instances to serve simple requests. Just as one user clicking
>> around our site I can get GAE to spin up 4-5 instances... and many of those
>> requests are painfully slow warmup requests.
>>
>> It feels almost like concurrency is broken. Maybe Google is rolling out
>> 1.8.5 with max_concurrent_requests but accidentally picked a default of
>> 1 instead of the usual 10?
>>
>> One thing is that we have recently moved to maven, modules, and an ear
>> package (it was a very painful process, I'm sad to say). I'm not sure how
>> we could have done something to break the scheduler though.
>>
>> Jeff
>>
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Google App Engine SDK 1.8.5 is now available!

2013-09-30 Thread Wolfram Gürlich 
There's one feature mentioned in the pre-release that unfortunately didn't 
make it to the final version. From the pre-release notes:

- The max_concurrent_requests setting is now configurable per 
version/engine.  
http://code.google.com/p/googleappengine/issues/detail?id=7927

Could that mean that someone is finally working on a scheduler overhaul and 
that some day we will wake up in a world where warm and cold instances can 
peacefully live together? Sorry, got carried away...

But wouldn't it be nice if we could set a lower and upper bound for 
max_concurrent_requests 
where new instances would be started as soon as all instances exceeded 
their lower bound and no request would be routed to a cold instance as long 
as there's one instance left which hasn't reached it's upper bound? 
Wouldn't that solve the cold start problem?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Concurrency broken?

2013-09-30 Thread Nicolas Fonrose (Teevity) 
Hi Jeff,

For the last three weeks, we are seeing quite the opposite of what you 
describe here ! This is a very good surprise to us because we are usually 
facing the problem you describe (many instances being started for no 
apparent reasons).

Over these three weeks, our app has literaly been flying, not sending any 
user facing requests to starting instances. The number of instances started 
hasn't really reduced compared to the previous month, but 98% of them are 
sent to already running so our users don't experience high latency.

We haven't got any hard facts to draw conclusion on why this has changed, 
but we've got the feeling that this might be due to an external system we 
have recently added (not running on AppEngine) and that sends regular 
requests to our app (several requests per minutes), thus generating not 
high but very regular traffic to the app.

If this can help other AppEngine/Java users solve the well known 
"high-latency on user facing requets" issue ...

Nicolas


On Saturday, September 21, 2013 11:29:04 PM UTC+2, Jeff Schnitzer wrote:
>
> Yesterday and today (and possibly longer) our (Java) app is spinning up 
> quite a few instances to serve simple requests. Just as one user clicking 
> around our site I can get GAE to spin up 4-5 instances... and many of those 
> requests are painfully slow warmup requests.
>
> It feels almost like concurrency is broken. Maybe Google is rolling out 
> 1.8.5 with max_concurrent_requests but accidentally picked a default of 1 
> instead of the usual 10?
>
> One thing is that we have recently moved to maven, modules, and an ear 
> package (it was a very painful process, I'm sad to say). I'm not sure how 
> we could have done something to break the scheduler though.
>
> Jeff
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.