similar to: debuggingState() analogous to tracingState() ?

Can you run rdebug on specs? I get errors when I try: $ rdebug spec ./spec/models/select_option_spec.rb ./spec: Is a directory - ./spec (Errno::EISDIR) from /opt/local/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/bin/ rdebug:136:in `debug_load'' from /opt/local/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/bin/ rdebug:136 from /opt/local/bin/rdebug:16:in `load''

How do I use the ruby debugger with a specific test (not the whole spec file)? I want to do something like this. $ rdebug spec/models/user_spec.rb -s "should error if not new_record" ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search.

I''m getting an exception that I''m fairless clueless about. It occurs when I run a "create" action but neither my action or before filters are hit before this exception. I''m hoping someone can give me a clue. I suspect it has to do with marshalling objects in the session - maybe TzTime is not capable of being stored in the session. I hope that''s not the

Dear list, here is a problem I met when trying to use a method for an S4 object, without loading the package in which the method was defined. I do not know if this is a bug, or a mistake of mine. Normally, I think the package in which the appropriate method is defined is loaded automatically when calling the method. The problem is that if the package is indeed loaded automatically, the

trace() seems to be broken in 2.6.1 and R-devel: Try the example from the ?debug man page: > library(methods) > trace("plot", browser, exit=browser, signature = c("track", + "missing")) Error in getFunction(what, where = whereF) : no function "plot" found Okay, it's just an example that doesn't work. Let's try a simpler one,

debugonce() sets a different flag (RSTEP), and this is not queried by isdebugged(), and it is also not unset by undebug(). Is this expected? If yes, is there a way to query and unset the RSTEP flag from R code? ? f <- function() { } ? debugonce(f) ? isdebugged(f) [1] FALSE ? undebug(f) Warning message: In undebug(f) : argument is not being debugged ? f() debugging in: f() debug at #1: { }

On Mon, May 21, 2018 at 5:01 PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: [...] > Do you have a good use case when it would be useful to query/unset the > mark for debugonce? Well, I suppose the same use cases when it is useful to query/unset the other debug mark. To be more specific, in debug helpers for a tool that works with callbacks from a central event loop, it is

This is interesting. The default rspec rake tasks generated by Hoe give you an rspec.rake file that looks like: > begin > require ''spec'' > rescue LoadError > require ''rubygems'' > require ''spec'' > end > So far so good. When you invoke rake to do something, say check_manifest > rake check_manifest > You

The problem: users trying to debug Mechanize apps with Komodo are finding the debugger times out once it''s loaded a web page. They don''t run into this in the ruby-debug debugger, or running in normal mode. The reason: Komodo''s debugger is graphical, which means that whenever it hits a breakpoint it automatically shows the contents of each local variable. It has a

When trying to debug a Rails 3 app with RadRails 2.0.4, I''m running into a problem with gem loading, apparently. See below for a stack trace. That problem disappears, when I move Gemfile out of the way, but, of course, then other necessary gems aren''t loaded. From my Debug Configuration Project: <myproject> File: script/rails Working Directory:

Hi, by switching to MySQL from SQLite, it fixed the problem. I ran rdebug on it and it is trying to call I ActiveRecord::Base.connection.begin_db_transaction. from ActiveRecordSafetyListener.scenario_started. I don''t think SQLLite likes transactions. Ed On Nov 15, 2007 10:56 AM, Ed Howland <ed.howland at gmail.com> wrote: > If I run the story stand-alone, I get: > ruby

Hi. I can''t seem to get debugging of specs working in Netbeans. AFAIK, I''m supposed to be able to just do Command+Shift+F5 with the spec open in the editor but i get this error: /Users/admin/src/expresso/vendor/plugins/rspec/lib/spec/test/unit/autorunner.rb:2:in `remove_method'': method `process_args'' not defined in Test::Unit::AutoRunner (NameError)

My autotest runs but when I make changes to a spec it doesn''t reload. I checked another application I was building that had 1.0.9 but it was reloading fine. How would I debug a problem such as autotest not reloading? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070930/6be7160d/attachment.html

Henrik, If a minimal reprex is hard to construct, could you perhaps instrument your version of R to include a browser() call at the start of the else if(!all(signature[omittedSig] == "missing")) { branch, run the code that triggers the issue for you (and must hit that branch) and tell us what the "signature" and "omittedSig" objects look like at that point?

**Maybe this bug needs to be understood further before applying the patch because patch is most likely also wrong** Because, from just looking at the expressions, I think neither the R 3.6.0 version: omittedSig <- omittedSig && (signature[omittedSig] != "missing") nor the patched version (I proposed): omittedSig <- omittedSig & (signature[omittedSig] !=

Hi all, I know I shouldn't really expect the following to work, but it provokes a crash of the GUI on my computer (Win xp professional). --- >sessionInfo() Version 2.3.1 (2006-06-01) i386-pc-mingw32 attached base packages: [1] "methods" "stats" "graphics" "grDevices" "utils" "datasets" [7] "base"

Thank you. To correct myself, I can indeed reproduce this with R --vanilla too. A reproducible example is: $ R --vanilla R version 3.6.0 Patched (2019-05-31 r76629) -- "Planting of a Tree" ... > Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "true") > loadNamespace("oligo") Error in omittedSig && (signature[omittedSig] != "missing") :

I''m having issues with WxRuby segfaulting when it''s dealing with external data in one form or another. I can reliably force WxRuby to crash by a) Parsing a file with Hpricot into an internal array of objects and assigning that to an instance variable on a Wx::Frame b) Running my script in Eclipse in "debug" mode and merely mousing over the

>>>>> Michael Lawrence >>>>> on Fri, 30 Nov 2018 08:24:31 -0800 writes: > Argument matching is by name first, then the still missing > arguments are filled positionally. Unnamed missing > arguments are thus left missing. Does that help? Thank you, Michael! Unfortunately, it may not help sufficiently notably once this thread will be

But the main point is where arguments are mixed together: > debugonce(plot.default) > plot(x=1:10, y=, 'l') ... Browse[2]> missing(y) [1] FALSE Browse[2]> y [1] "l" Browse[2]> type [1] "p" I think that's what I fall over mostly: that named, empty arguments behave entirely different from omitting them (", ,") And I definitely agree we need