Console displays 0 deployments for project with non-zero deployments in the presence of stuck spinner

[mikeb26]

I seem to have created a project state which results in the console incorrectly reporting that my project has 0 deployments when it has several dozen. Via CLI:

$ bopmatic deploy list --projid proj-a3698921c9b114c3
Listing deployments for project proj-a3698921c9b114c3...
DeploymentId
dply-7adfd2d3cea8c391
dply-436ec1b1de359257
dply-2903d7db8d5097c7
dply-df06642bcef62916
dply-197831cc356209be
dply-80246176afa16c2e
dply-5a467d2166ca1553
dply-f70bccffba5ca60a
dply-53857d3dd9945c00
dply-e150760ec625830c
dply-e2db7198dda59835
dply-09105d2b5e0c59a7
dply-454a06a71b0cc4ee
dply-a4f697238bef9ccd
dply-9bbe4b94f0cd9d39
dply-f0362f226eca8c36
dply-75a246cb996a9ea9
dply-bec64dcf411e59fd
dply-4c3c3e190ff818ca
dply-f350fe73d0ec5717
dply-8dda5aa760a14d07
dply-d943c0e21acd76a6
dply-4abe6acb0bf280e4
dply-23a6e0a59c439377
dply-5396d95a1c6176e8
dply-8ebdb1d0a0fe8899
dply-4753311ff8909dda
dply-79cd0ede95f85e90

However the console shows attached:

Interestingly the label for the Deployments tab correctly shows that there are 28, which is consistent with the CLI. But the content of the deployments tab says there are no deployments. I have a strong suspicion that this bug is a 2nd order consequence of a stuck production state spinner as I have only seen this occur when that bug is also occuring (#31).

Ideally the fix for this issue (as distinct from #31) results in the deployments tab being correctly populated despite the presence of a stuck spinner. If the content of the deployments tab is currently dependent upon the production state spinner resolving first, ideally that dependency would be removed. Please also note the same problem occurs with the packages tab but I won't bother filing a separate issue as I suspect it is the same root cause.