Re: [racket-dev] [plt] Push #24460: master branch updated
Two days ago, sa...@racket-lang.org wrote: a390019 Sam Tobin-Hochstadt sa...@racket-lang.org 2012-03-24 14:31 : | Improve filter for `path-string?'. : M collects/tests/typed-racket/unit-tests/typecheck-tests.rkt |2 ++ M collects/typed-racket/base-env/base-env.rkt|4 +++- Looks like it's still just a union: (: x : Path-String) (define x foo\0bar) (define (foo) (delete-file x)) And I get no errors from that. Maybe at least document it as something that doesn't correspond to `path-string?'? -- ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: http://barzilay.org/ Maze is Life! _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] Serious problem
Hi, Today (i.e., 3/26/2012) DrRacket version 5.2.1 no longer starts. Instead, it signals an error on function read-bitmap. This bug was initially reported by a colleague of mine and then independently confirmed by me. Given that the bug only showed today, and it doesn't occur when we change the current date of the computer, this looks like some kind of Easter egg that went wrong, probably, related to prince-kuhio-day. This is annoying, to say the least, but the most serious effect is on the credibility of the Racket ecosystem. I've put a lot of effort in doing research on top of Racket and I tried hard to convince my colleagues of the usefulness of Racket. However, it has been increasingly difficult to keep up with its instabilities. You can guess what my colleagues will say... Best, António Leitão. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Serious problem
Dear António (and your colleagues), My apologies. I will build better automated testing support for the various easter eggs and we are working on an short-term fix. I know it is not possible to repair lost credibility, and for that I'm deeply disappointed with myself. Robby On Mon, Mar 26, 2012 at 5:06 AM, Antonio Menezes Leitao antonio.menezes.lei...@ist.utl.pt wrote: Hi, Today (i.e., 3/26/2012) DrRacket version 5.2.1 no longer starts. Instead, it signals an error on function read-bitmap. This bug was initially reported by a colleague of mine and then independently confirmed by me. Given that the bug only showed today, and it doesn't occur when we change the current date of the computer, this looks like some kind of Easter egg that went wrong, probably, related to prince-kuhio-day. This is annoying, to say the least, but the most serious effect is on the credibility of the Racket ecosystem. I've put a lot of effort in doing research on top of Racket and I tried hard to convince my colleagues of the usefulness of Racket. However, it has been increasingly difficult to keep up with its instabilities. You can guess what my colleagues will say... Best, António Leitão. _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] today's DrRacket problem
Dear Racket users, Many of you noticed that DrRacket v5.2.1 refused to launch today, March 26. We sincerely apologize for this inconvenience. The problem is due to a so-called Easter egg, which is a visual surprise that one developer builds into the code for the others and our users -- a tradition going back to the early days of our project. The bug affects only DrRacket, no other Racket software. As far as version 5.2.1 is concerned, it will disappear tomorrow, but it will return later this year. For the upcoming release -- due out before the next easter egg date -- we will either install much more reliable test methods for the Easter eggs or we will remove them entirely. More immediately, we offer the following workarounds for the DrRacket bug: * Revert to version 5.2: http://download.racket-lang.org/racket-v5.2.html * In your current installation of 5.2.1, navigate to the following folder: collects - drracket - private remove the file drracket-normal.rkt and replace it with the corrected copy at http://www.cs.utah.edu/plt/fix/drracket-normal.rkt * For those of you with commandline tool experience, download a Racket patch file from http://www.cs.utah.edu/plt/fix/patch-for-v5.2.1.plt navigate in your shell to the folder with the 5.2.1 executables, and install the patch with ./raco setup -A where specifies a path to the downloaded file. As much as we prepare and test these Easter eggs, software obeys only one law: what can go wrong will go wrong eventually. We definitely should have been more careful. Once again, we regret any problems we caused you today -- Matthias Felleisen, for PLT _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] today's DrRacket problem
On Mon, Mar 26, 2012 at 10:11:06AM -0400, Matthias Felleisen wrote: Many of you noticed that DrRacket v5.2.1 refused to launch today, March 26. We sincerely apologize for this inconvenience. The problem is due to a so-called Easter egg, which is a visual surprise that one developer builds into the code for the others and our users -- a tradition going back to the early days of our project. The bug affects only DrRacket, no other Racket software. As far as version 5.2.1 is concerned, it will disappear tomorrow, but it will return later this year. For the upcoming release -- due out before the next easter egg date -- we will either install much more reliable test methods for the Easter eggs or we will remove them entirely. I vote to keep the easter eggs. Software will always break, abit of fun does the psyche good. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] today's DrRacket problem
oh, cool. I like easter eggs. This was no chocolate though. :p On Mon, Mar 26, 2012 at 11:11 AM, Matthias Felleisen matth...@ccs.neu.edu wrote: Dear Racket users, Many of you noticed that DrRacket v5.2.1 refused to launch today, March 26. We sincerely apologize for this inconvenience. The problem is due to a so-called Easter egg, which is a visual surprise that one developer builds into the code for the others and our users -- a tradition going back to the early days of our project. The bug affects only DrRacket, no other Racket software. As far as version 5.2.1 is concerned, it will disappear tomorrow, but it will return later this year. For the upcoming release -- due out before the next easter egg date -- we will either install much more reliable test methods for the Easter eggs or we will remove them entirely. More immediately, we offer the following workarounds for the DrRacket bug: * Revert to version 5.2: http://download.racket-lang.org/racket-v5.2.html * In your current installation of 5.2.1, navigate to the following folder: collects - drracket - private remove the file drracket-normal.rkt and replace it with the corrected copy at http://www.cs.utah.edu/plt/fix/drracket-normal.rkt * For those of you with commandline tool experience, download a Racket patch file from http://www.cs.utah.edu/plt/fix/patch-for-v5.2.1.plt navigate in your shell to the folder with the 5.2.1 executables, and install the patch with ./raco setup -A where specifies a path to the downloaded file. As much as we prepare and test these Easter eggs, software obeys only one law: what can go wrong will go wrong eventually. We definitely should have been more careful. Once again, we regret any problems we caused you today -- Matthias Felleisen, for PLT _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] today's DrRacket problem
Many of you noticed that DrRacket v5.2.1 refused to launch today, March 26. We sincerely apologize for this inconvenience. Checking: can a reference to this announcement be on the front page of the racket-lang web site? _ Racket Developers list: http://lists.racket-lang.org/dev
