ClimateDataCalculation

[krambriw]

I think I was too quick, I suspect the bug is still there... investigating....but only presentation issue

[Mastiff]

OK, bad! With the latest version EG stops after a few minutes! Can you please upload the one before again? I didn't save it...

[Mastiff]

Panic over. The worst of it anyway. I deactivated the report generation, and it seems to work without it. I think I can take a few hours or days without the reports.

[krambriw]

New versions uploaded,looks ok for me, no high cpu

[Mastiff]

Still locks up. I have my reports generating 60 seconds after startup of EG, and less than a minute after that EG just stops receiving events, with a yellow icon. And 96 % CPU use...

[Mastiff]

There's no doubt that it's the reports. It's now been running for half an hour without any problems with the reports deactivated.

[krambriw]

I better say 'I think I have' solved the problem...

I suspect the problem was because I changed to use the python library 'thread' instead of 'threading' (the code became a bit simpler) but I think 'threading' is recommended to use, 'thread' is superseeded or outdated. Anyway, my tests are now working fine, I re-create reports every minute and it looks good here

New version is uploaded

[Mastiff]

I spoke too soon. I discovered by accident that it had locked up late last night. So there's still something strange there, even though it takes a lot longer before it has effect.

[Mastiff]

The previous message was writen while you wrote your message, so not about the new version. But this is about the new version: I have the now traditional locked database error a few seconds after startup and while creating the reports, but now it keeps on ticking for a few seconds more. There are three error messages on the reports, then a bunch of stuff comes in at once, and then it all stops, with around 50-70 % CPU but no excessive memory use. On exit from EG it manages to close the process itself after a minute or so. Oh, just to make sure I deleted everything in the directory before I did this upgrade, so all the files are the latest version (at least they should be).

[krambriw]

Yes,
I think the problem is related to accessing the db both for writing (saving incoming) and reading (creating report) at the same time, I think I will try to make a kind of semaphore so that while report creation is ongoing, saving data is put on hold

[Mastiff]

Sounds good!

[krambriw]

It's looking good here, I think I will have a new version ready for tomorrow (I just would like testing during the night...)

[Mastiff]

If you could share today that would be nice. I'm leaving the cabin around noon tomorrow to go home and do some remodelling there (selling next year, so the house needs to look presentable when we show it), and I won't be back here for a week or so. So if you have something you have faith in, I could start running that now and check until I go to bed (which is around six hours, longer than any of the earlier versions have taken to stop working).

[krambriw]

OK, fine, I'll upload now in a few seconds. Here it is really working fine

[krambriw]

Done