Re: [MacRuby-devel] Rake exceptions always print a full trace
Nope, you’re not missing anything, that’s a bug. Please file a ticket for it. On Oct 2, 2011, at 2:45 AM, Josh Abernathy wrote: > I wanted to verify that I'm not crazy and I'm not doing something stupid > before I create a ticket for this. > > The `rake` that comes with MacRuby (both 0.10 and the nightly) seems to > always print a full trace when a task raises an exception. For example, if I > run: > > task :blah do > raise Exception, 'whatev' > end > > With MacRuby, I get: > > rake aborted! > whatev > /Volumes/GitHub/Mac/blah/rakefile:2:in `block' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:632:in > `block' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:629:in > `execute' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:595:in > `block' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/monitor.rb:201:in > `synchronize' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:588:in > `invoke_with_call_chain' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:581:in > `invoke' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2042:in > `invoke_task' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in > `block' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in > `block' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2059:in > `standard_exception_handling' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2014:in > `top_level' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:1993:in > `run' > /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/bin/macrake:31:in > `' > > If I run with Ruby 1.9.2, I get: > > rake aborted! > whatev > > Tasks: TOP => blah > (See full trace by running task with —trace) > > And if I use Ruby 1.9.2 and run `rake` with —trace, I get an output like that > of MacRuby. So MacRuby seems to *always* print the full trace, regardless of > whether I include the —trace flag. This is pretty annoying when running tests > because of the constant visual noise when I get a failed test. > > Am I missing something? Is there any way to suppress the trace? > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] [ANN] RailsMailPreview released
This looks very helpful, thanks! Met vriendelijke groet, Eloy Durán On Sep 30, 2011, at 4:56 AM, Fernando Barajas wrote: > Hi I just finished RailsMailPreview is now available on github > Feel free to check out.. https://github.com/fernyb/RailsMailPreview > > Thanks > - Fernando > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] REXML UTF-8 Encoding not found
Did you include the standard library when running macruby_deploy? If you are excluding it, then you should be able to fix this with passing this to macruby_deploy: `--stdlib rexml`. On Oct 3, 2011, at 6:32 AM, saugust wrote: > Hi Everyone, > > I am trying to deploy an app that uses XMLSimple and I am getting an error > when I try to run the app on computers other than my own. > > Here is the error message: > > 11-10-02 9:14:17.289 PM [0x0-0x39039].com.blah.blah: > /Users/me/Desktop/MyApp.app/Contents/Resources/rb_main.rb:18:in `block': no > such file to load -- rexml/encodings/UTF-8.rb (LoadError) > > The only difference I can see is my development machine is running ruby 1.9.2 > and the test environment is still at 1.8.6. Should the REXML be looking to > the MacRuby framework? I am using XMLSimple as a file in my app not a gem. > > Any suggestions would be greatly appreciated. > > Thank you, > > Shaun > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] Rake exceptions always print a full trace
Thanks, filed: https://www.macruby.org/trac/ticket/1399 On Oct 5, 2011, at 12:20 AM, Eloy Durán wrote: > Nope, you’re not missing anything, that’s a bug. Please file a ticket for it. > > > On Oct 2, 2011, at 2:45 AM, Josh Abernathy wrote: > >> I wanted to verify that I'm not crazy and I'm not doing something stupid >> before I create a ticket for this. >> >> The `rake` that comes with MacRuby (both 0.10 and the nightly) seems to >> always print a full trace when a task raises an exception. For example, if I >> run: >> >> task :blah do >> raise Exception, 'whatev' >> end >> >> With MacRuby, I get: >> >> rake aborted! >> whatev >> /Volumes/GitHub/Mac/blah/rakefile:2:in `block' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:632:in >> `block' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:629:in >> `execute' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:595:in >> `block' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/monitor.rb:201:in >> `synchronize' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:588:in >> `invoke_with_call_chain' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:581:in >> `invoke' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2042:in >> `invoke_task' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >> `block' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >> `block' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2059:in >> `standard_exception_handling' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2014:in >> `top_level' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:1993:in >> `run' >> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/bin/macrake:31:in >> `' >> >> If I run with Ruby 1.9.2, I get: >> >> rake aborted! >> whatev >> >> Tasks: TOP => blah >> (See full trace by running task with —trace) >> >> And if I use Ruby 1.9.2 and run `rake` with —trace, I get an output like >> that of MacRuby. So MacRuby seems to *always* print the full trace, >> regardless of whether I include the —trace flag. This is pretty annoying >> when running tests because of the constant visual noise when I get a failed >> test. >> >> Am I missing something? Is there any way to suppress the trace? >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] Odd crash message
I haven’t done this myself yet, but I think you’ll have to hack on rakelib/builder/options.rb a bit to select the 10.6 SDK, or alternatively build the framework from source on a 10.6 machine. On Oct 4, 2011, at 5:21 PM, Nick Ludlam wrote: > Hi all, > I'm building a MacRuby app on Lion, and then getting testers to run it on > Snow Leopard, and I'm seeing the following symbol problem: > > dyld: Symbol not found: __dispatch_queue_attr_concurrent > Referenced from > MyApp.app/Contents/MacOS/../Frameworks/MacRuby.framework/Versions/Current/usr/lib/libmacruby.dylib > Expected in: flat namespace > > I'm guessing this is a GCD thing. On my system, this seems to be provided by > /usr/lib/libobjc.A.dylib, but is this not the case on SL installs? > > I'm using MacRuby HEAD, if that has any bearing on things, but if anyone has > an idea as to the problem, I'd be very grateful! > > > Nick > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Re: [MacRuby-devel] Rake exceptions always print a full trace
Oops, didn’t check the recent messages :) @Watson/Mark: I will remove that `or true` part, but let’s wait with upgrading rake until after 0.11, unless Laurent gives the go ahead. On Oct 5, 2011, at 9:29 AM, Josh Abernathy wrote: > Thanks, filed: https://www.macruby.org/trac/ticket/1399 > > > On Oct 5, 2011, at 12:20 AM, Eloy Durán wrote: > >> Nope, you’re not missing anything, that’s a bug. Please file a ticket for it. >> >> >> On Oct 2, 2011, at 2:45 AM, Josh Abernathy wrote: >> >>> I wanted to verify that I'm not crazy and I'm not doing something stupid >>> before I create a ticket for this. >>> >>> The `rake` that comes with MacRuby (both 0.10 and the nightly) seems to >>> always print a full trace when a task raises an exception. For example, if >>> I run: >>> >>> task :blah do >>> raise Exception, 'whatev' >>> end >>> >>> With MacRuby, I get: >>> >>> rake aborted! >>> whatev >>> /Volumes/GitHub/Mac/blah/rakefile:2:in `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:632:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:629:in >>> `execute' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:595:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/monitor.rb:201:in >>> `synchronize' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:588:in >>> `invoke_with_call_chain' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:581:in >>> `invoke' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2042:in >>> `invoke_task' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2020:in >>> `block' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2059:in >>> `standard_exception_handling' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:2014:in >>> `top_level' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/lib/ruby/1.9.2/rake.rb:1993:in >>> `run' >>> /Library/Frameworks/MacRuby.framework/Versions/0.11/usr/bin/macrake:31:in >>> `' >>> >>> If I run with Ruby 1.9.2, I get: >>> >>> rake aborted! >>> whatev >>> >>> Tasks: TOP => blah >>> (See full trace by running task with —trace) >>> >>> And if I use Ruby 1.9.2 and run `rake` with —trace, I get an output like >>> that of MacRuby. So MacRuby seems to *always* print the full trace, >>> regardless of whether I include the —trace flag. This is pretty annoying >>> when running tests because of the constant visual noise when I get a failed >>> test. >>> >>> Am I missing something? Is there any way to suppress the trace? >>> ___ >>> MacRuby-devel mailing list >>> [email protected] >>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> >> ___ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > ___ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel ___ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
