Thanks for the report. That was me, trying to implement Display create date on Selected Best Nodes. It's hard to work on, because there is caching... and because one particular pmdev from years ago wrote code in a style which is -- shall we say -- not optimized for maintainability. ;-)

All of the problems that I confirmed/reported yesterday have now gone away. Thanks for fixing, resolving, or whatever you did.

— Ken

This is intended as a confirmation of this problem and what others have mentioned. I've added some additional information.

Best nodes for Day, Week and Month have three instances of:

Internal problem occurred in get_picked_nodes
called with 10 bind variables when 9 are needed
[download]

Best nodes for Year has different problems:

• First column with heading "#", which I believe used to have 1 to 20, now shows "1618135679" for all 20 rows.
• The next three columns ("Node", "Author" and "Rep") look normal.
• Column 5 with heading "CrDt" is new. It has the numbers 0 to 19 (increasing sequentially for each of the 20 rows). I don't know what this is supposed to be but is possibly related to what marto wrote.

Worst nodes has four instances of:

Internal problem occurred in get_picked_nodes
called with 10 bind variables when 9 are needed
[download]

This is what hippo reported.

I also got a lot of "500 Internal Server Error" messages when accessing a variety of pages. I managed to clear these with one or two refreshes. Some examples: "Worst Nodes"; "Newest Nodes"; "RFC: Better Best Answers Gets Real".

The Categorized Questions and Answers section has been decommissioned, note the extra column in the best/worst nodes.

It appears not to be limited to nodelets, Best Nodes is currently showing the same for daily, weekly and monthly. Worst Nodes is showing it for all categories.