[google-appengine] Re: urlfetch and another type of communication

2009-04-17 Thread Ben Nevile

And hello again.

So I woke up this morning to see that the issue had been marked
resolved, and that you determined that the spike did not affect your
customers.  I was furious!  But then I actually took the time to
carefully debug my application, and I see that in fact the problem was
mine.  I was trying to fetch a URL with an unescaped space in it.

I'm sorry that I'm such a tool.  My cred is out the window at this
point I know, but if you want to stem future frustration from and for
idiots like me, a more helpful error message would be a good place to
start.  Here's the trace that pops out now:

preTraceback (most recent call last):
  File quot;/base/python_lib/versions/1/google/appengine/ext/webapp/
__init__.pyquot;, line 501, in __call__
handler.get(*groups)
  File quot;controllers/migration.pyquot;, line 187, in get
x = p.points100_in_between_dates(datetime(2009,4,14),datetime
(2009,6,14))
  File quot;models/player.pyquot;, line 49, in
points100_in_between_dates
stats = self.stats_in_between_dates(start_date,end_date)
  File quot;models/player.pyquot;, line 41, in
stats_in_between_dates
stats = json.read(urlfetch.fetch(url).content)
  File quot;/base/python_lib/versions/1/google/appengine/api/
urlfetch.pyquot;, line 267, in fetch
raise DownloadError(str(e))
DownloadError: ApplicationError: 2



How about BadUrlError or something like that?

Ben




On Apr 16, 10:21 pm, Ben Nevile ben.nev...@gmail.com wrote:
 So I'm aware that Google is aware that there are urlfetch issues
 tonight.  At least, that's what I'm lead to believe at the GAE System
 Status page, where the problem has been marked as Anomaly for the
 last 5 hours or so.  But I have no feedback other than that.

 Please Google, I'm sorry to whine at you, but I need a little
 feedback.  Should I be making adjustments to my software to reduce
 dependency on urlfetch?  Is there a team of people figuring out what's
 wrong, or just one lonely, frantic person?  Was there a fire?

 You are a big animal and I am just a small gnat, trying to make a
 living by riding on your back.  Perhaps that was an unwise choice.  It
 cost me more money to host at my last place, but at least in a
 situation like this I could make a phone call.

 Ben
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---



[google-appengine] Re: urlfetch and another type of communication

2009-04-17 Thread Matthew Blain

Hi Ben,
Thanks for raising these, sorry if this was frustrating, it would be a
good feature to expose a more specific error here.

As for the status site page, indeed it was not an issue directly in
app engine or urlfetch. The site we were pointing the urlfetch test to
had an issue, and the status site cannot itself distinguish between
the remote server having issues and urlfetch having issues. The other
test on the urlfetch status page reported almost 100% success at that
time. You are correct that it would have been helpful if we'd noted
that at the start of the investigation rather than the end.

--Matthew

On Apr 17, 9:06 am, Ben Nevile ben.nev...@gmail.com wrote:
 And hello again.

 So I woke up this morning to see that the issue had been marked
 resolved, and that you determined that the spike did not affect your
 customers.  I was furious!  But then I actually took the time to
 carefully debug my application, and I see that in fact the problem was
 mine.  I was trying to fetch a URL with an unescaped space in it.

 I'm sorry that I'm such a tool.  My cred is out the window at this
 point I know, but if you want to stem future frustration from and for
 idiots like me, a more helpful error message would be a good place to
 start.  Here's the trace that pops out now:

 preTraceback (most recent call last):
   File quot;/base/python_lib/versions/1/google/appengine/ext/webapp/
 __init__.pyquot;, line 501, in __call__
 handler.get(*groups)
   File quot;controllers/migration.pyquot;, line 187, in get
 x = p.points100_in_between_dates(datetime(2009,4,14),datetime
 (2009,6,14))
   File quot;models/player.pyquot;, line 49, in
 points100_in_between_dates
 stats = self.stats_in_between_dates(start_date,end_date)
   File quot;models/player.pyquot;, line 41, in
 stats_in_between_dates
 stats = json.read(urlfetch.fetch(url).content)
   File 
 quot;/base/python_lib/versions/1/google/appengine/api/urlfetch.pyquot;, 
 line 267, in fetch
 raise DownloadError(str(e))
 DownloadError: ApplicationError: 2

 How about BadUrlError or something like that?

 Ben

 On Apr 16, 10:21 pm, Ben Nevile ben.nev...@gmail.com wrote:

  So I'm aware that Google is aware that there areurlfetchissues
  tonight.  At least, that's what I'm lead to believe at the GAE System
  Status page, where the problem has been marked as Anomaly for the
  last 5 hours or so.  But I have no feedback other than that.

  Please Google, I'm sorry to whine at you, but I need a little
  feedback.  Should I be making adjustments to my software to reduce
  dependency onurlfetch?  Is there a team of people figuring out what's
  wrong, or just one lonely, frantic person?  Was there a fire?

  You are a big animal and I am just a small gnat, trying to make a
  living by riding on your back.  Perhaps that was an unwise choice.  It
  cost me more money to host at my last place, but at least in a
  situation like this I could make a phone call.

  Ben
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---