I'm starting to try out GetBundles, but I see the following error in its log:
01/24/2009 18:08:21 TextMate[GetBundles] GetBundles' DIALOG runs at token 1
deadlock 0x5b5c0c: sleep:F(10) - /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:583 deadlock 0x341ac: sleep:F(15) (main) - /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:137 /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:789:in `getResultFromDIALOG': Thread(0x5b750c): deadlock (fatal) from /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:1165
01/24/2009 18:09:06 TextMate[GetBundles] Timeout while connecting Bundle Server
What could cause this? I've deleted Bundles/GetBundles.tmbundle and reinstalled with svn co, but the same thing happens...
On 25.01.2009, at 00:10, Jay Levitt wrote:
deadlock 0x5b5c0c: sleep:F(10) - /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:583 deadlock 0x341ac: sleep:F(15) (main) - /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:137 /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb: 789:in `getResultFromDIALOG': Thread(0x5b750c): deadlock (fatal) from /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb: 1165
01/24/2009 18:09:06 TextMate[GetBundles] Timeout while connecting Bundle Server
What could cause this? I've deleted Bundles/GetBundles.tmbundle and reinstalled with svn co, but the same thing happens...
Could you please tell me the following info:
- Mac OSX version and (Intel/ppc) - svn version (svn --version) - Ruby version (ruby -v)
It seems to me that the error was caused by the attempt to get the url from a local installed bundle which was installed by using svn.
--Hans
Hans-Jörg Bibiko wrote:
On 25.01.2009, at 00:10, Jay Levitt wrote:
`getResultFromDIALOG': Thread(0x5b750c): deadlock (fatal) from /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb: 1165
Could you please tell me the following info:
- Mac OSX version and (Intel/ppc)
Intel 10.5.6 (Mac Pro, early 2008)
- svn version (svn --version)
svn, version 1.5.5 (r34862)
- Ruby version (ruby -v)
ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]
On 27.01.2009, at 21:32, Jay Levitt wrote:
Hans-Jörg Bibiko wrote:
On 25.01.2009, at 00:10, Jay Levitt wrote:
`getResultFromDIALOG': Thread(0x5b750c): deadlock (fatal) from /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb: 1165
Could you please tell me the following info:
- Mac OSX version and (Intel/ppc)
Intel 10.5.6 (Mac Pro, early 2008)
- svn version (svn --version)
svn, version 1.5.5 (r34862)
- Ruby version (ruby -v)
ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]
Since I've learnt from James Gray in that list: http://www.nabble.com/Re:-(NoMethodError)-with-TODO-Bundle-p21689534.html
that using Ruby 1.8.7 is tricky I'd suggest first to set up your environment in such a way that
/usr/bin/env ruby -wKU
calls Ruby 1.8.6 (default on Leopard) and try to run GetBundles again.
--Hans
Hans-Jörg Bibiko wrote:
Hans-Jörg Bibiko wrote:
On 25.01.2009, at 00:10, Jay Levitt wrote:
`getResultFromDIALOG': Thread(0x5b750c): deadlock (fatal) from /Users/jay/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb: 1165
- Ruby version (ruby -v)
ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]
Since I've learnt from James Gray in that list: http://www.nabble.com/Re:-(NoMethodError)-with-TODO-Bundle-p21689534.html
that using Ruby 1.8.7 is tricky I'd suggest first to set up your environment in such a way that
/usr/bin/env ruby -wKU
calls Ruby 1.8.6 (default on Leopard) and try to run GetBundles again.
Ah hah! I uninstalled the MacPorts version of Ruby, and GetBundles now works fine. I'd seen a few problems under 1.8.7, but I assumed they were all my fault (or older Rails versions); I didn't realize that it was a hybrid of 1.8 and 1.9 functionality with such common compatibility problems.
Learned my lesson. Thanks.
Jay