SVN Beacon Needs a Timeout
Reported by Geoffrey Grosenbach | May 16th, 2007 @ 12:39 PM
The standard SVN beacon fails to connect sometimes. I do a commit, all the files are sync'ed, and then it hangs. Sometimes I kill the svn client and later find curl sitting on my SVN server trying to ping a dozen revisions ago.
http://lighthouseapp.com/help/se...
Maybe adding --max-time 30 to the curl hit would let curl timeout instead of waiting forever and never connecting?
I use Net::Http in a capistrano post-deploy message and never have any problems. Maybe this would be a better route?
Comments and changes to this ticket
-
rick July 27th, 2007 @ 09:20 PM
I suppose. The beacon is just a quick example I came up with. My
original used activeresource (which of course uses net/http
internally), but I didn't like the idea of requiring a gem just to
ping LH.
It's a bit troubling that you're timing out though. I don't have
issues, but it's all within the Engineyard network (though svn and
lighthouse are separate slices).
-
-
-
Will May 4th, 2008 @ 11:21 PM
- → State changed from “new” to “open”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Using Lighthouse to track Lighthouse.
