We have a new server we are about to start using. I believe we have the most recent version of the NPL (though maybe I'm supposed to call it the OPL now - I'm a bit confused about whether they are different, or if this is a renaming).
I just reran OPL-update a few minutes ago though, so the version seems current.
I've run across several NPL problems that we use in some of our standard homework sets that no longer work, and in fact cause a big problem.
They claim to be placeholders for the same problem, now stored in another location. The problem is the "other location" they refer to simply refers back to the file. So when WeBWorK attempts to render these problems it loads the file, which tells it to lead the file, ... creating an infinite loop. Of course not only are the results bad, but this brings the server to an unfortunate near stall.
I guess there are two issues:
1) appropriate for this forum: what has gone wrong that the NPL has these self referential problems in it. Is my install screwed up, or are these just mistakes in the NPL and I've been unlucky enough to run across three of them in half an hour?
2) maybe belonging in a different forum: should WeBWorK be coded to break out of such infinite loops much sooner?
Here are examples of offending problems:
/opt/webwork/libraries/NationalProblemLibrary/Union/setLimitConcepts/s1_3_19.pg
/opt/webwork/libraries/NationalProblemLibrary/Union/setLimitConcepts/s1_3_27.pg
/opt/webwork/libraries/NationalProblemLibrary/Utah/AP_Calculus_I/set2_Derivatives_and_Limits/1210s2p27.pg
I'm attaching the file of the first of the three problems above. All of these files
are similar. They are almost empty but have an includePGproblem that seems
to be self-referential.
Anyone know if my NPL installation is screwed up, or if these are just errors.
If they are just errors, how might I identify them more globally. As it is right
now, every time anyone stumbles on them, they do something nasty to
the server.
thanks, Hal