I go to Report>Recent Operations and I see an empty table (even though I know I recently executed some operations). So I click the "refresh" button and the table finally populates with the data.
Don't think this is as high a priority as other issues.
I made this a high priority because this may be a canary-in-the-mine - this is not the first time I saw behavior like this, so this could be an indication of a wider problem across the board. We need to look at the Table implementation that changed recently (re: initial criteria/fixed criteria) and make sure either a) nothing is broken or b) we need subclasses to use the new initial criteria feature.
In other words, this is more than just a bug in Reports>Recent Operations, we need to investigate if the underlying Table component implementation and its usages are broken in other places.
Author: Jay Shaughnessy <email@example.com>
Date: Thu Apr 21 09:59:45 2011 -0400
An async issue that could result in the totalRows of a fetch not being
initialized (and therefore set to 0). The fetch itself was successful, but
the Response was wrong if the timing was right.
Verified on build#28 (Version: 4.0.0-SNAPSHOT Build Number: da7bcb0)
Executed some operations on a resource and verified that the Report>Recent Operations page displays the recent operations without hitting the Refresh button.
Marking as verified.
Bookkeeping - closing bug - fixed in recent release.