Busted my stack!

> /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:667:in `traverse_some_element’: stack level too deep (SystemStackError)
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `traverse_some_element’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `each’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `traverse_some_element’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `traverse_some_element’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `each’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `traverse_some_element’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `traverse_some_element’
        from /usr/lib/ruby/gems/1.8/gems/hpricot-0.8.2/lib/hpricot/traverse.rb:668:in `each’
         … 3844 levels…

Dalibor Nasevic had the fix…

my settings: stack size (kbytes, -s) 10240

> ulimit -s 51200

my settings: stack size (kbytes, -s) 51200

And all my stack busting issues are resolved🙂

 

Posted via web from ChrisDrit’s Ruby Rambler

Japanese Addresses

November 28, 2009

…and other opposites

My colleagues and I are looking for alternative client tools for Mac OS X.

Nowadays, I tell people to take twice what they think they need, especially if they’re doing this for the first time.

But rather than raise a bunch of money and waste it on something that we was unproven, we chose to launch with the smallest possible feature set and just see what happened. The results were awesome.

In 6 weeks we signed up over 200 paying customers, were featured on several popular blogs, and had a ton of great feedback and ideas from our users. It worked just like Steve Blank said it would. But as time has progressed and we have continued to sign up users at a faster rate than we anticipated, we have struggled to keep up. Much of the struggle is because of the way the customer development process works, and the dark side that no one talks about.

One of my favorite habits of journalists is that they refuse to state an opinion. Instead, they find a source to say whatever it is they want said and then quote them. And when I say “favorite,” what I really mean is that I hate it.

Webloyalty Scam

November 28, 2009

Interesting, shows a few examples of people that do not review their credit card statements and how Webloyalty auto-charges on consumers credit cards via an obfuscated, permission based, authorization (the cc info has already been collected from another site).