[racket-dev] getting "oops, internal error" messages when updating PLaneT packages

I think I found the bug. The problem I found was that, during the
creation of the rss feed (the rss feed shows the recently added
packages), the planet server was not being careful enough to guard
against bad xexprs in package info.rkt files.

Well, I didn't find any packages that would actually lead to that
specific error which is a bit mysterious, but the error at that spot
is consistent with you seeing the package actually be uploaded
successfully (and the logfile that I can see), and is the only place
where I see a call to that function (which is actually named
write-xml/content) with non-checked input.

So hopefully you won't see that error anymore. Thanks for the report.

Robby

On Mon, Aug 15, 2011 at 6:21 PM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> I think that this is the relevant part of the log, showing the error:
>
>  Monday, August 15th, 2011 5:38:17pm:
>   write-xml-content: received ()
>  Monday, August 15th, 2011 6:02:19pm:
>   write-xml-content: received ()
>
> I'm not seeing a stacktrace (probably because I have a bug in my
> logging). I don't see anything obviously wrong with the packages,
> either.
>
> I'll have to look into this more later on but at least for the moment,
> I think that things are in shape. Please let me know if you spot
> something wrong (as that would be a clue as to where that error is
> coming from!).
>
> Thanks,
> Robby
>
> On Mon, Aug 15, 2011 at 5:04 PM, Danny Yoo <dyoo at cs.wpi.edu> wrote:
>> I'm updating a few of my PLaneT packages and trying to eliminate
>> compile-time errors that have been bugging the heck out of me.  When I
>> update the package, I'm seeing the following error message from
>> PLaneT's web site:
>>
>> ---
>>
>> Oops! An internal error occured. The problem has been logged, but if
>> you have any further information to report, please email
>> planet at racket-lang.org.
>>
>> ---
>>
>> I've updated both my version-case.plt and closure-compile.plt
>> libraries today.  Is there any other debugging information I can
>> provide?
>> _________________________________________________
>>  For list-related administrative tasks:
>>  http://lists.racket-lang.org/listinfo/dev
>>
>