Hi Eric, For now you should be able to overcome this issue by requesting a much smaller amount of results per page -- you might find a sweeter spot with some of these queries at 20 to 40 rpp -- it's simply timing out building a result set for you at that quantity.
@episod <http://twitter.com/intent/user?screen_name=episod> - Taylor Singletary On Mon, Jun 20, 2011 at 8:34 AM, Eric Mueller <nevin...@gmail.com> wrote: > I noticed some 500 responses to our search api requests this morning that > were oddly consistent - specific queries that would always error, when most > queries never (rarely) do. > > I started trying to reproduce with smaller queries, and arrived at a few > examples. > > This search fails with a 500 error: > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.75,-84.37,12.35mi > It probably should be returning an empty results list (notice the 12 mile > radius). > > The same search with the decimals chopped off the latitude woks fine (empty > results as expected): > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33,-84.77,12.35mi > > Removing the decimals from the longitude instead doesn't work: > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.25,-84,12.35mi > > *Changing* the value of the decimal digits on the latitude sometimes works, > and sometimes doesn't: > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84,12.35mi > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.44,-84,12.35mi > > Changing the value of the decimal digits on the longitude doesn't seem to > produce failures no matter what I put in. > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.01,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi> > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.44,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber%20OR%20jersey%20shore%20OR%20young&geocode=33.01,-84.99,12.35mi> > > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=bieber&geocode=33.44,-84.99,12.35mi > fails, > but > > http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&geocode=33.44,-84.99,12.35mi<http://search.twitter.com/search.json?rpp=100&lang=en&result_type=recent&q=palin&geocode=33.44,-84.99,12.35mi> > (geocode > only) works fine. > > I tested a few of these without rpp, lang, and result_type params with > identical results, so you can probably disregard those. > > These aren't random failures - every time I try one of the failing queries, > it continues to fail (though that may change as the result set changes over > time). > Are there any known bugs with the geocode handling in the search api? > > - Eric > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
