Hi all! If you're on Python App Engine and you need to use an
OAuth-protected API on another site, check out oauth-dropins. It’s a
collection of drop-in OAuth client flows for many popular sites, including
Facebook, Twitter, Google+, Instagram, Dropbox, Blogger, Tumblr, and
WordPress.com, with
me too. it seems like many dynamic requests, if not all, are spawning new
instances. very odd. seems like the scheduler is unhappy.
On Thursday, May 8, 2014 10:00:59 PM UTC-7, James Foster wrote:
>
> I'm seeing the same thing. Between 10x and 30x the regular number of
> instances, even though th
hi all! just FYI, it looks like Instagram is blocking/rate limiting App
Engine's IPs from fetching www.instagram.com, both urlfetch and sockets,
across apps. e.g. this session from https://shell-hrd.appspot.com/ :
>>> urllib2.urlopen('https://www.instagram.com/snarfed/')
Traceback (most recent c
; Nick
> Cloud Platform Community Support
>
> On Monday, May 2, 2016 at 11:57:15 AM UTC-4, Nickolas Daskalou wrote:
>>
>> Hi Ryan,
>>
>> It seems to be working fine for us (SocialPage.me
>> <https://socialpage.me/>).
>>
>> Are you accessing thei
Ls like eg
https://www.instagram.com/p/BE4xLpmABFz/.
i used to do 3-5x that much before i throttled down recently. i
haven't tried, but i expect i could ramp back up to that on the
reverse proxy and not get 429ed.
> On Thursday, May 5, 2016 at 6:36:12 PM UTC-4, Ryan Barrett wrote:
>&
hi all! starting around 3PM PST yesterday, my instances have started
crashing on a small fraction of requests, much more often and consistently
than before. (app id s~brid-gy.) the log message is the usual, "A problem
was encountered with the process that handled this request, causing it to
exi
looks like this has stopped as of around 1pm PST today. app engine team, if
this was a 1.9.13 bug that got fixed, thank you!
On Monday, October 6, 2014 8:54:04 AM UTC-7, Ryan Barrett wrote:
>
> hi all! starting around 3PM PST yesterday, my instances have started
> crashing on a small
just a heads up: this started happening again a few hours ago. my instances
are on 1.9.14 now, and the timing and situation are about the same, so
maybe the same root cause with the new release?
On Tuesday, October 7, 2014 4:39:03 PM UTC-7, Ryan Barrett wrote:
>
> looks like this has stop
...and stopped again, as of 12:30 PST.
On Monday, October 20, 2014 11:28:25 AM UTC-7, Ryan Barrett wrote:
>
> just a heads up: this started happening again a few hours ago. my
> instances are on 1.9.14 now, and the timing and situation are about the
> same, so maybe the same root ca
...nd started again a few hours ago, i'm guessing due to the
introduction of 1.9.15.
apologies for harping on this; it just continues to be an interesting
new(ish) pattern, at least to me.
On Tuesday, October 21, 2014 5:30:11 PM UTC-7, Ryan Barrett wrote:
>
> ...and stopped agai
looks like yesterday's 1.9.19 release raised the limit on string properties
in the datastore from 500 to 1500 chars. awesome!
from google/appengine/api/datastore_types.py:
_MAX_STRING_LENGTH = 1500
tested in https://shell-27.appspot.com/ :
>>> from google.appengine.ext import db
>>
hi all! a number of us have started seeing twitter API errors in prod GAE
in the last week or so. write calls and some search calls are returning
HTTP 401 {"errors":[{"code":32,"message":"Could not authenticate you."}]}
for all users with no code changes on our end. the particularly odd part
eing generated differently in prod vs. dev, due to a
>> difference in some built-in python library on the prod server, and that
>> will be much more difficult to debug since the timestamp and nonce prevent
>> you from comparing dev vs prod requests character-by-character.
>&
On Wednesday, April 29, 2015 at 11:29:34 AM UTC-7, Ryan Barrett wrote:
>
> as another data point, there may be more to it than just punctuation
> characters. i see the error with pretty much any tweet content and
> username. i reproduced it just now by attempting to tweet "
On Thursday, April 30, 2015 at 1:10:23 PM UTC-7, Waleed wrote:
>
> Another update. It seems that the issue is happening in App Engine release
> 1.9.20. Some of the instances in my app are on this release, and others are
> on the previous 1.9.19. We didn't a full scan, but based on manual
> inspe
...on an unrelated note, 1.9.20 was *way* better with utilization and
scheduling instances efficiently for my app. app engine team, i hope that part
survives!
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group
On Friday, May 1, 2015 at 4:13:03 PM UTC-7, Waleed wrote:
>
> My app was also rolled back to 1.9.19 yesterday. Then later it was back on
> 1.9.20, but the error seems to have been fixed. I also got email
> confirmations from customers that they're not seeing this problem any more.
> Great team w
thanks for the reply!
On Fri, Nov 8, 2019 at 2:40 PM 'Andrew Gorcester' via Google App Engine <
google-appengine@googlegroups.com> wrote:
> I would recommend trying to solve the first problem and serving static
> files locally.
>
understood, but using a different static file server is not great.
hi alex! you're right to be cautious, but happily, requests are not
handled by different threads. our python interpreters are single
threaded, and handle only a single request at a time. more:
http://code.google.com/appengine/docs/python/sandbox.html
http://groups.google.com/group/google-appengin
On Feb 19, 11:26 am, Rein Petersen wrote:
>
> root() Returns a model instance for the root (top parent) entity
> within the entity chain of this instance, or None if this instance
> does not have a parent
interesting! that would definitely be useful. you don't need a
dedicated new app engine fea
20 matches
Mail list logo
