Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Internal problem in Montly/Weekly Best

by Discipulus (Abbot)
on Apr 12, 2021 at 08:32 UTC ( #11131124=monkdiscuss: print w/replies, xml ) Need Help??

hello pmdevs

I noticed the following error in nodelets about Montly/Weekly Best, maybe there is some work in progress?

Monthly Best Internal problem occurred in get_picked_nodes called with 10 bind variables when 9 are needed Weekly Best Internal problem occurred in get_picked_nodes called with 10 bind variables when 9 are needed

L*

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Replies are listed 'Best First'.
Re: Internal problem in Montly/Weekly Best
by jdporter (Canon) on Apr 12, 2021 at 13:41 UTC

    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. ;-)

    I reckon we are the only monastery ever to have a dungeon staffed with 16,000 zombies.

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

      — Ken

Re: Internal problem in Montly/Weekly Best
by kcott (Bishop) on Apr 12, 2021 at 10:21 UTC

    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

    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

    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".

    — Ken

Re: Internal problem in Montly/Weekly Best
by marto (Cardinal) on Apr 12, 2021 at 08:38 UTC
Re: Internal problem in Montly/Weekly Best
by hippo (Chancellor) on Apr 12, 2021 at 08:36 UTC

    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.


    🦛

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://11131124]
Approved by Corion
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (3)
As of 2021-07-28 08:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?