Calculate package scores and the score report from stable versions where possible

From https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/2873
We should calculate package (and the score report) from our "significant version" rather than from the default branch. Xcode imports the stable version, then a pre-release, then default branch if no tagged versions exist, so the score should be based on that.

I just looked at this with @supersonicbyte and this feature makes less sense when we look in detail at it.
It makes logical sense to look at stable versions as that's what people tend to use, but we do not have historical data snapshots of repository data at the point of stable versions.
Rather than try and mix the sources of data for the score calculation, we should always calculate from the default branch. This is the current behaviour, and so no changes are necessary.
Problem solved 😂


Traceback error when running exporter

Hi,
I tried to run exporter and getting traceback error:
2020-06-08 13:14:52,885 INFO:Starting web server on port 9272
2020-06-08 13:15:02,413 ERROR:Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 1838, in _async_render_GET
    yield self.generate_latest_metrics(request)
KeyError: 'specs_size'

I created my own container image from git. I get the same error if I pull image from docker hub, just different line.
2020-06-08 12:41:37,372 INFO:Starting web server on port 9272
2020-06-08 12:42:44,539 ERROR:Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 1638, in _async_render_GET
    yield self.generate_latest_metrics(request)
KeyError: 'specs_size'

Any idea what could be the cause?
Thanks

What version are you on?>

The default is 5000, if you set the value to specs_size: 5000 does it still error?

I'm having the same issue on VMWARE ESXi 7.0.  Where do I set this?

I'm having the same issue on VMWARE ESXi 7.0.  Where do I set this?

same issue on vCenter 7.0

closed for staleness. Readme shows how to set these values.