I've been reading perlmonks all morning, but node_id=784237 Find prime number between 1 to 1000000 has been timing out. I can read the replies, but not the node. Weird.

Replies are listed 'Best First'.
Re: Can't read node_id=784237
by Corion (Patriarch) on Jul 30, 2009 at 22:49 UTC

    I "fixed" Find prime number between 1 to 1000000 - it was an open spoiler+code tag in BrowserUk's post that got truncated once it got written to the DB and then read back. While the node remained in the node cache, it wasn't truncated, after the DB roundtrip it was. The rendering code there needs to become more robust. It likely dove into a long backtracking regex where it should have quit.

Re: Can't read node_id=784237
by Limbic~Region (Chancellor) on Jul 30, 2009 at 00:01 UTC
    Anonymous Monk,
    I too have the same problem but can assure you that it worked fine earlier in the day (since I replied to the root node myself). I am sure that the admins have their hands busy with other things but if it is still messed up tomorrow I will mention it in the CB.

    Cheers - L~R

Re: Can't read node_id=784237
by Khen1950fx (Canon) on Jul 30, 2009 at 07:51 UTC
    If you try to view the node normally, then you would do the normal thing by trying http://www.perlmonks.org/?node_id=784237, but I tried it, and it's not going anywhere. Now if you try http://www.perlmonks.org/?displaytype=edithistory;node_id=784237, you'll get the node which says:

    "This node has not been edited yet"

    It seems somebody went to edit it and then forgot about it:-).

Re: Can't read node_id=784237
by FunkyMonk (Bishop) on Jul 29, 2009 at 22:38 UTC
    It was OK earlier today, but now it's timing out for me as well.