Kevin, hopefully you are looking at the good thing now. :-)
Here's what I'm using:
${HTTPS}www.worldcommunitygrid.org/api/members/<membername>/results?code=<code>&format=json&ServerState=5&SortBy=CpuTime&Offset=0&Limit=0
It is currently returning 0 results, as lavaflow mentioned, although there are results available.

This is what I get:

{"ResultsStatus": {
    "ResultsAvailable": "327",
    "ResultsReturned": "0",
    "Offset": "0",
    "Results": [
]
}
}

I think 'Limit=0' was never official. Can it officially be used from now on (as soon as it works again )?
EDIT: To retrieve the maximum number of results allowed, of course.

What about trying to retrieve a negative number of records? Well, at least it works! That is, you'll get all — to the maximum extent permitted — available results:

{"ResultsStatus": {
    "ResultsAvailable": "327",
    "ResultsReturned": "327",
    "Offset": "0",
    "Results": [
…

… is what I get when using limit=-1.

I found the behavior. In hibernate, when "setMaxResults" is called with a 0 or negative number, the behavior is not defined. In the older version of hibernate setting it to 0 would return all results. In the new version, 0 returns 0 results. As you observed a negative value will also return all results.

However, there is discussion that they might make it an error to call the function with 0 or lower.

In order to preserve the behavior and make limit=0 official, I've modified the code so that if limit is 0 or less, then setMaxResults is not set and therefore all results will be returned. This code will be on production in the next 30 minutes or so. I'll post when it is available.

Many thanks for the arduous labor. 😎