MichaelHoward comments on Issues, Bugs, and Requested Features - Less Wrong

10 Post author: Eliezer_Yudkowsky 26 February 2009 04:45PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (628)

You are viewing a single comment's thread.

Comment author: MichaelHoward 25 March 2009 01:03:56PM 2 points [-]

I get "Error encountered" in place of my user page. Other people's seem fine. It was OK yesterday.

Comment author: dclayh 26 March 2009 07:46:59PM 2 points [-]

I am now getting this error also. Only my own user page, only when I'm logged in.

Comment author: MichaelHoward 25 March 2009 05:44:26PM *  2 points [-]

This is now fixed. I'll leave the comment in case it happens to others.

<Edit> - Error happened again, then gone again a few hours later. Happened both at home and work, happens for a while, no apparent link between occurrences, logging out doesn't fix it.

<Edit 28Mar> - Now happening all the time. Still not fixed by logging out. I can see dclayh's page (mentioned above). This is potentially very serious if it keeps spreading.

For affected users, you can still see replies to your comments here, and possibly still http://lesswrong.com/user/<you>/submitted/, /liked/, /disliked/, /hidden/ and /drafts/.

<Edit 31 Mar> Can now access my user page after 3 days broken, but can't get to page 2 of my comments. So it looks like it's breaking trying to display some type of comment on user the page, and fixed when said comment dropped to page 2. Maybe a certain combination or nesting of editing flags confuses it?

<Edit 31 Mar> Broken again, but can access all pages that don't list my comments. The only comments I made/edited since it worked are this one, this one, this one and this one, but clearing the comments out doesn't fix it.

<Edit 1 Apr> 1st page of comments accessible again, and all 4 of the above comments are on that page. Go figure.

<Edit 2 Apr> Broke again, no comments made since last worked.... ...Working again, again no comments made.

Comment author: wmoore 08 April 2009 12:28:00AM 1 point [-]

We deployed a fix yesterday that addresses this problem. The bug was influenced by the caching that is employed, which is why it happens sometimes but not others.

Comment author: MichaelHoward 08 April 2009 12:06:09PM *  0 points [-]

I can confirm this is fixed for all pages of mine that were broken. Thank you :)

Comment author: gwern 25 March 2009 03:23:49PM 1 point [-]

I've been seeing that error while logged-in periodically as well. But I can't seem to reproduce it reliably, so I haven't reported it.