[google-appengine] Re: Heartbleed bug?

As I understand it, the post says that App Engine was vulnerable to Heartbleed. Given this, its possible that private keys for custom domains could have leaked, so does Google recommend that we change these keys? I realize I probably just answered my own question, I was just hoping for some mo

[google-appengine] Re: What to do with a bad instance?

The only way to deal with it at the time (because you couldn't kill > instances) was to wrap the entire handler in a try block, and if you got an > import error inside the handler > I would allocate enough memory to kill the instance. > > Cheers > > Tim > > On Thurs

[google-appengine] What to do with a bad instance?

Every so often (once a month or less), I get an instance that just doesn't work. Every request fails with some error in library code that indicates something is profoundly screwed up, like an import fails or some line of obviously correct code throws an exception. When this has happened in the

[google-appengine] Re: NDB strategy for keeping caches in sync with the datastore

Thanks for writing this up. I had been trying to figure this out myself. I think your reasoning is correct. There is also the case of deleting an entity from one client and another client causing it to be added back to memcache. _LOCKED should help in that case too. I think the key to all this

[google-appengine] Re: major MEMCACHE changes started October 5th

I see this bug as well. Dedicated memcache is in preview release, so bugs like this shouldn't be surprising. I filed an issue: https://code.google.com/p/googleappengine/issues/detail?id=10108 On Friday, October 11, 2013 10:42:18 AM UTC-4, James Gilliam wrote: > > Now there is a billing issue wi

[google-appengine] Re: major MEMCACHE changes started October 5th

I filed a production issue on this. I suggest everyone who is seeing this problem do the same. I also switched the dedicated memcache service until this is fixed. so far so good. On Thursday, October 10, 2013 2:58:37 PM UTC-4, James Gilliam wrote: > > Here is what I know so far ... > > I ran th

[google-appengine] Re: major MEMCACHE changes started October 5th

I'm experiencing the same thing as you. A few months of reliable memcache, but now since the weekend I'm seeing the cache reset every couple of hours and a lower hit rate. Nothing changed in my app (haven't deployed in a few days). On Tuesday, October 8, 2013 1:24:12 PM UTC-4, James Gilliam wro

[google-appengine] Re: ImagesService getServingUrl fails often

On Tuesday, September 17, 2013 12:56:26 PM UTC-4, Mac wrote: > Hi, > > We have a java app that calls ImagesService to get a serving url > via getServingUrl API call > > I notice we get ImagesServiceFailureException A LOT. > > Has anyone come across this? > In my experience its one of the less rel

[google-appengine] Broken blobstore files - what to do?

I've noticed a bunch of images that my users have uploaded to blobstore are inaccessible. When I try to view the file in the dashboard Blob Viewer, I get a 500 error. I can't download or access the data in any way. I've filed a production issue on this but have not heard back. I've only recent

Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

On Saturday, August 24, 2013 11:12:35 AM UTC-7, muhamma...@k2-labs.com wrote: > Thanks Vinny P for your reply, > > I have increased the number of idle instances from Automatic to 100 and > lower the minimum pending latency slider from Automatic to 100ms. I will > update in few days if I faced t

Re: [google-appengine] BREACH attack - is App Engine vulnerable?

system is compressing data from > mixed sources (for example, XSRF token and the user input). if you’re > designing a system which both compresses and encrypts data, please keep in > mind the lesson from this attack and avoid compressing mixed data. > > We'll try to share an upda

[google-appengine] Re: BREACH attack - is App Engine vulnerable?

On Wednesday, August 7, 2013 3:26:29 PM UTC-4, Chad Vincent wrote: > I'm with the person from Iron Mountain... Just like CRIME, they both seem > to require some kind of XSS vulnerability in the page, then take advantage > of TLS and GZIP. As long as your users don't use a lot of suspicious >

[google-appengine] BREACH attack - is App Engine vulnerable?

Can someone from Google make a statement on whether App Engine is vulnerable to the BREACH attack that was announced recently? http://breachattack.com/ I'm not a security expert, but it looks like you are vulnerable to the attack if you use both SSL/TLS and HTTP compression. Since that configu

[google-appengine] Re: 1.8.3 Pre-Release SDKs are now available.

On Monday, July 29, 2013 9:26:04 PM UTC-4, Richmond Manzana wrote: > - Fixed an issue with debugger/breakpoint not working on the dev_appserver. > > http://code.google.com/p/appengine-devappserver2-experiment/issues/detail? > id=28 > http://code.google.com/p/googleappengine/issues/detail?

Re: [google-appengine] Running App Engine Instance 1.8.2

On Tuesday, July 16, 2013 12:27:30 PM UTC-4, Chris Ramsdale wrote: > in regard to the issues related to App Engine Modules (previously > "Servers") and 1.8.2, you were seeing the side effects of a name change > ("Servers" => "Modules") that took place with the 1.8.2 rollout. i had > sent out a

[google-appengine] 1.8.2 causes exceptions with older mapreduce library versions

My app is in the process of being upgraded to 1.8.2, but its causing tons of errors because I use an older version of the mapreduce library which imports google.appengine.api.servers. It looks like that module no longer exists in 1.8.2. I've created an issue for this: https://code.google.com/p

Re: [google-appengine] Some questions about get_serving_url.

On Wednesday, July 10, 2013 6:17:54 AM UTC-4, barryhunter wrote: > > The image should get a future expires date, so the browser will cache the > image. > FYI, the expiration time is 24 hours, and there doesn't seem to be a way to change this. https://groups.google.com/d/topic/google-appengine

[google-appengine] Re: Is it possible for a transactional db.get() to return a stale result if a recent transaction raised a “special” exception?

On Tuesday, June 11, 2013 2:04:17 PM UTC-4, Vinny P wrote: > If a transaction exception occurs though (as you asked in your original > post) there is no guarantee that the transaction occurred. In that case, > you may receive stale data because the transaction is delayed/never > occurred. > Th

[google-appengine] Re: Is it possible for a transactional db.get() to return a stale result if a recent transaction raised a “special” exception?

On Tuesday, June 11, 2013 12:51:46 PM UTC-4, Vinny P wrote: > For now, let's ignore the transaction and exception details. Suppose you > make a simple datastore put, then immediately query the datastore for that > entity. There's a good chance that the entity that you just put in won't > exist,

Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.

On Saturday, June 8, 2013 2:04:23 AM UTC-4, Chris Ramsdale wrote: > what would keep you from migrating over to a Cloud Storage-based solution? > 1. Its a bit of a pain to get set up with cloud storage, especially all the service name account and permissions stuff. Blobstore is nice because it j

[google-appengine] Re: Noobie: Sharing a collection of in-memory objects between instances.

On Thursday, June 6, 2013 5:27:59 AM UTC-4, Mohammad Al Quraian wrote: > > I'm just starting with GAE, so bare my ignorance. My app is using a > in-memory list that is accessed very often by font-end clients, my solution > before was to use a static list. After gaining more info on GAE I know now

[google-appengine] Re: App Engine Release 1.8.0 in dashboard

the issue in this case is more that you guys are running code that's not yet in prerelease. I thought the way it worked was that you would put out a prerelease version that we could play with and at the same time, upgrade some apps/instances in production to see if there were any issues. in this

[google-appengine] Re: pull queues and backend basics

On Tuesday, April 30, 2013 4:35:18 PM UTC-4, Vinny P wrote: > For resident backends, AppEngine ensures that a backend is always running. > It's dynamic backends that start up/shut down in response to requests. > > Of course, it's always a good idea to periodically monitor your resident > backend

[google-appengine] pull queues and backend basics

Hi, My app creates many tasks which send data to a web service. Currently each task POSTs its data independently, I would like to batch these in a single http request to reduce load on the service. It seems like pull queues and backends would be great for this, but I'm a little unsure about ho

[google-appengine] Different python ProtocolBuffer implementations on dev and prod

Hi, I've been pickling some data to store in a datastore blob, and recently I tried to download and unpickle the data on my local machine. I got errors whenever I tried to do this because it seems like production uses a different version of ProtocolBuffers than the SDK. Part of the pickled dat

Re: [google-appengine] Re: Important for Python developers - Updates to the Development Server in 1.7.6

On Friday, March 22, 2013 12:35:37 PM UTC-4, Kaan Soral wrote: > No one forces anyone to use anything, you can always use previous versions > of SDK/Devappserver > > They've stated why It's currently not possible to debug with > devappserver2, as someone watching the development of devappserver2

Re: [google-appengine] Re: Important for Python developers - Updates to the Development Server in 1.7.6

On Thursday, March 21, 2013 12:50:20 AM UTC-4, Andrew Jessup wrote: > > If you'd like to take a look now, I would point you to this discussion > https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28and > in particular the document linked there that summarizes our propos

[google-appengine] Re: Very large entity ids on 1.7.6 dev server

On Thursday, March 21, 2013 5:10:30 AM UTC-4, Jesse Rohwer wrote: > We are aware of this issue and will have it fixed before we release > scattered ids in production. Does this mean that scattered ids will become the default id generation strategy in production? How does that affect allocate_i

[google-appengine] Re: Still getting blank page for Datastore Admin link

On Sunday, March 17, 2013 12:45:10 PM UTC-4, Carl Schroeder wrote: > Using Go appengine 1.7.4 SDK. > Tried disabling and enabling datastore admin. > Supposedly this was fixed. > > Ideas anyone? > This can happen if you are logged into more than 1 google account at the same time. You can go dire

[google-appengine] Re: Blobstore filename created in MapReduce job too long to create BlobKey

On Friday, March 1, 2013 11:25:17 PM UTC-5, Jamie Niemasik wrote: > Some of the filenames are 288 bytes long, while some are 992. The M/R spec > name and id in each case is nearly the same and is very short; I don't see > where this variance comes from. > Have you noticed if the long file names

[google-appengine] latency and pending_time in RequestLog

I posted this question to stackoverflow[1], but there seems to be more activity here, so I'm going to repost it. There are a few timing fields in the App Engine RequestLog[2] class. How are they defined? My guess is this: latency = end_time - start_time total request time = pending_time + lat

[google-appengine] Re: Query speed benchmarks

On Saturday, February 23, 2013 4:59:45 PM UTC-7, GAEfan wrote: > So, let's say I wanted to make a version of Twitter. If I wanted to > search for any tweets in the datastore with a certain #hashtag, that seems > best handled asynchronously. Speed is important there. What to do? > Running a

[google-appengine] Re: Query speed benchmarks

On Saturday, February 23, 2013 2:46:55 PM UTC-7, GAEfan wrote: > Has anyone run any speed tests for querying different model types (ndb, > db, django.db)? > > I like NDB, but am considering using Django (non-rel) for a new app. > Django models and queries would be most transportable, but I do

Re: [google-appengine] Re: Our application is very slow and appengine.google.com is unreachable

I'm still seeing timeouts. Also, the app engine status page is timing out for me as well. On Tuesday, January 15, 2013 11:38:09 AM UTC-5, Christina Ilvento wrote: > > Hi All, > > We had a brief > issue

[google-appengine] Re: Web site completely down + appengine console not accessible

On Friday, October 26, 2012 11:18:00 AM UTC-4, Damian del Rivero Lagunes wrote: > My Apps are also down. http://code.google.com/status/appengine is also > down. i was able to load the status page after a long wait. here's a screenshot in case anyone is curious:

[google-appengine] Re: Custom expires/cache-control for get_serving_url images

blobstore api). In fact, this could be even better as there would be fewer > domain names to look up. > > On Friday, August 31, 2012 12:21:25 AM UTC+2, Alex Burgel wrote: >> >> I've noticed that image urls generated by get_serving_url are set to >> cache for only 24

[google-appengine] Custom expires/cache-control for get_serving_url images

I've noticed that image urls generated by get_serving_url are set to cache for only 24 hours. Is it possible to change this? 24 hours isn't very long, especially considering that the images can't change. The Page Speed proxy service caches for 1 year, thats much more reasonable. -- You receiv

[google-appengine] Re: Unique Integer ID for a non primary key field for Entities in Google App Engine

Forget the compress part. Hash instead, SHA1 or something. You would need to store and index the hashed value in that row so you can query for it. On Monday, August 6, 2012 11:07:34 AM UTC-4, Alex Burgel wrote: > > You could compress then base64 the url and use that value to share. &g

[google-appengine] Re: Unique Integer ID for a non primary key field for Entities in Google App Engine

You could compress then base64 the url and use that value to share. Also, questions like this should probably go to stackoverflow. You're more likely to get a useful response there. On Monday, August 6, 2012 9:41:19 AM UTC-4, Neo wrote: > > Any one?? -- You received this message because you ar