Closed solipsist01 closed 3 years ago
Hi @solipsist01,
I can confirm this is a bug; I would say this is a bug that has always been there and wasn't specifically introduced in one version or another.
I have pushed a new build which should hopefully resolve this issue. Can you please try it out via the manual installation instructions?
Thanks for all your patience with this; there have been at least three incidents where separate people that have experienced issues with this feature; with each new issue that pops up I add several new unit tests to cover those edge cases; there are only so many edge cases you can have, so at some point there will finally be no more issues! Right? :P In any case, the crazy value combinations your PRTG server spits out are really helping to solidify this feature.
Regards, lordmilko
Hi @lordmilko
I already tested the new build. The bug has vanished ;) Thank you !
Perhaps we now have reached the point of no more issues, indeed ! :) I will keep testing the feature, as the script runs every month to generate new reports, and we keep adding more and more.
At some point, perfection will be reality indeed :)
Hi, @Lordmilko
It seems that version 0.9.16 introduced a new bug in the parsing in get-sensorhistory The error is however diffrent from the error we had in https://github.com/lordmilko/PrtgAPI/issues/218 I've tried to gather info as complete as possible. if you need anything, i'll provide :)
The following code now generates an error:
RAW XML Output from PRTG: from url: https://someprtg/api/historicdata.xml?id=51483&edate=2021-06-04-11-31-08&sdate=2020-06-04-11-28-54&avg=2678400&sortby=-datetime&coun t=500&username=redacted&passhash=redacted