this shouldn't happen - feel free to give a sample of the "poison user" IDs, and we'll investigate them. we already have one, and we'll look into more.
On Sun, Apr 25, 2010 at 10:16 AM, Ryan Rosario <uclamath...@gmail.com>wrote: > I've found that all of my 500 isses are related to "poison users." For > whatever reason, I can never get their followers. I retry on 500, so I > end up with an infinite loop of 500s for these users. When 500s happen > with other users, my program usually succeeds after 1 or 2 retries. > > The only way to resolve it is to kill my process, add the user to a > blacklist, and start over. It's really frustrating. > > Ryan > > On Apr 25, 5:31 am, Dossy Shiobara <do...@panoptic.com> wrote: > > From my logged errors ... here's an example: > > > > http://api.twitter.com/1/users/show.xml?id=4583991 > > > > On 4/25/10 12:37 AM, Mark McBride wrote: > > > > > Without more details this is going to be really hard to troubleshoot. > > > Can you reliably reproduce this? What are the exact URIs you're > > > calling that return 500s? What user are you using to make these > > > calls? What authentication method? > > > > -- > > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > > Panoptic Computer Network |http://panoptic.com/ > > "He realized the fastest way to change is to laugh at your own > > folly -- then you can let go and quickly move on." (p. 70) > > > > -- > > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
