Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #1368 (closed defect: wontfix)

Opened 3 years ago

Last modified 3 years ago

Breakpoint fails without DRb

Reported by: bitsweat Assigned to: Florian Groß <flgr@ccan.de>
Priority: normal Milestone: 1.x
Component: Railties Version: 0.12.1
Severity: normal Keywords: breakpoint drb remote
Cc:

Description

Comment out BREAKPOINT_SERVER_PORT in config/environments/development.rb. Set a breakpoint in your code and run ./script/server. Load a page that hits the breakpoint. Your shell running ./script/server drops into irb but$stdout is not redirected, so whatever you do in your irb session has its invisible results sent to the browser.

Also, it'd be nice if Breakpoint.deactivate_drb actually meant "turn off DRb breakpoints, I don't want them." A subsequent Breakpoint.activate_drb call blithely ignores it and reactivates remote breakpoints. Perhaps a separate method is in order.

Change History

09/17/05 19:08:00 changed by anonymous

  • keywords changed from breakpoint drb remote to breakpoint drb remote fd.

09/28/05 04:31:36 changed by bitsweat

  • cc deleted.

Florian, do you have any suggestions here? I'm unfamiliar with breakpoint's internals.

10/12/05 22:59:12 changed by marcel

  • keywords changed from breakpoint drb remote fd to breakpoint drb remote.

No longer a final drive ticket.

11/15/05 09:12:57 changed by bitsweat

  • status changed from new to closed.
  • resolution set to wontfix.
  • milestone changed from 1.0 to 1.x.

Forget it, Florian is MIA, and this will be less useful as we move away from webrick for dev.

11/15/05 13:24:35 changed by Florian Groß

Heh, I only got a mail about this today and am not really watching bugs on here, anyway. A personal mail is usually the best way to go.

Regarding $stdout: You are supposed to use client.puts and so on for that kind of stuff as automatic redirection of the server's STDOUT could change the behavior of other applications (especially CGI ones, probably others as well).

I'm not sure I understand what is wrong about Breakpoint.deactivate_drb. As far as I remember it does what the documentation says it does which is also what I think it should do. If you want to stop other code from reactivating breakpoints I guess you could just do def Breakpoint.activate_drb(*) end which is somewhat of a hack.

So if I'm not overseeing anything there is nothing in this bug for me to do.

Oh, and it would be great if ruby-breakpoint was integrated over RubyGems or something similar. I'm not really sure if it is still true, but I think the Rails version is not completely in sync with the last release.

Oh, and yeah, I'm somewhat busy, but will still try to answer mails concerning my software in a timely manner.