Reports don't generate on 2.11.12

[primetheus]

The reports fail to generate in 2.11.12 unless adding the import calendar statement to Reports.py

[larsxschneider]

👋Thanks for the bug report! I can't reproduce the bug on 2.12.6 ATM (I don't have 2.11.12 to test right now). How do you generate the report? Via dedicated machine or on the appliance?

[primetheus]

I was running it on the appliance itself. I also didn't see it on 2.12.6, but appeared on 2.11.12 after upgrading 2.10.8->2.11.12

[primetheus]

It may be just an edge case... I'll test a bit more and close this one out if I can't produce it again with a new build

[IngoS11]

I am seeing the same issue with the 2.12.6 appliance and Hubble installed on a separate Ubuntu 16.04 with python 3.5.2. Hubble only runs if I add and import calendar in ReportPRUsage.py or in imported Report.py

[pluehne]

@primetheus, @IngoS11: We’ll investigate this further beginning of next week. Sorry for the delay!

[pluehne]

@primetheus, @IngoS11: Excuse me for having dragged this out for so long, but I’ve now added the missing import statement in #152.

[sky9723]

We using 2.12.5 GHE, in this instance hubble's current release version 0.2 don't works too.
it generate 2 issue

1. added meta.tsv, updated documentation, fixed calendar import #146 , missing meta.tsv at hubble-data
2. Add missing Python import directive #152, Reports don't generate on 2.11.12 #136 missing import calendar

after i make meta.tsv in hubble-data.git and add import caledar code at ReportPRUsage.py
our hubble reports tsv files (but i'm not still sure it works fully well)
thanks @pluehne @IngoS11
and i'll wating @larsxschneider 's release update :)

[pluehne]

@sky9723: We’ll be releasing a new version of Hubble in the next days, which will contain the recent fixes 🙂.

[pluehne]

@sky9723: We just released Hubble Enterprise 0.3.0 🙂.

[sky9723]

@pluehne Thanks, i'll install and report it works well or not

[sky9723]

@pluehne after 0.3.0, it is working well, at 2.12.5 & 2.13.2, thanks

[pluehne]

@sky9723: That’s great, and thanks for letting us know!