Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running a very simple (and contrived) call of:

I'm expecting a response of:


But am getting a response of:


Changing the filter to something else (default, etc) results in the expected information, so it's not a quota thing.

share|improve this question
This a pretty major bug, the total field returns 0 even with a custom filter. – Jonathan. Jan 3 '12 at 0:47
up vote 2 down vote accepted

Well, this was a fun one.

Basically, a number of methods were figuring out that you weren't asking for any fields on an object type (like, say, users) and short-circuiting around database queries. Unfortunately, there are also some methods that relying on the database queries to populate total. This generally happened in the "query by id" methods.

So, I disentangled those methods so that short-circuiting won't happen when a method is expecting to figure out the total from the resulting data.

A fix has been deployed.

share|improve this answer
Excellent, thank you! :) – Dave DeLong Jan 4 '12 at 0:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .