[racket-dev] reporting bugs from behind firewalls

From: Eli Barzilay (eli at barzilay.org)
Date: Wed Feb 15 08:39:53 EST 2012

Just now, Pierpaolo Bernardi wrote:
> oops. I have not tried sending this report with this version of
> DrRacket.  I was remembering the behaviour of previous versions.
> Should I try to file this report to check if it's working for me?

Please do -- it shouldn't do anything other than web stuff.

Just now, Matthias Felleisen wrote:
> You misunderstood. I don't want the poor dr to open any port or
> communicate with the outside. I want an option like in PDF
> previewers that says "send this info out via a mail client" and puts
> all the info into Mail.

I did understand that.  (The port forwarding is on the server, not
something that anyone else should know about.)

What I'm saying is that it's a significant effort to maintain two bug
reporting front-ends (one on the web and one via email), with little
benefit since systems that are closed for HTTP and open for email are
very rare.  (And possibly also not the case here.)

          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!

Posted on the dev mailing list.