TACTIC Open Source
TACTIC tickets on 4.8 - Printable Version

+- TACTIC Open Source (http://forum.southpawtech.com)
+-- Forum: TACTIC Open Source (http://forum.southpawtech.com/forumdisplay.php?fid=3)
+--- Forum: TACTIC Discussion (http://forum.southpawtech.com/forumdisplay.php?fid=4)
+--- Thread: TACTIC tickets on 4.8 (/showthread.php?tid=78)



TACTIC tickets on 4.8 - listy - 02-21-2020

Hi!

I have downloaded, and successful installed TACTIC 4.8 with material design theme. It is awesome! Can't wait to switch to it.
Just one bug i noticed - it generates tons of tickets. Even when i set 2+ years ticket expiry time.
Before my server failed i ran out of memory with 200 000+ tickets (it will be hard to erase it).
Python 3.7, latest tactic 4.8.

Bye!


RE: TACTIC tickets on 4.8 - listy - 04-23-2020

Anything on that?
Looks like it affects me on tactic 4.7 python 3.7 too...


RE: TACTIC tickets on 4.8 - listy - 04-24-2020

I just Looked closer. And it seems to be TACTIC creating one new ticket for admin login every ~10 seconds.
It starting to create tickets even after reboot.
And it creates one ticket per each running TACTIC process.
Is it something happening with monitor?


RE: TACTIC tickets on 4.8 - listy - 04-24-2020

So in my case - this is batch.py
From where Batch is called - not an easy task


RE: TACTIC tickets on 4.8 - remkonoteboom - 04-24-2020

I looked into this. It was a scheduled task that was introduced to do some reloading of cached data in the background. It was creating a new ticket on every execution. I have adjusted it so that it reuses the main batch ticket.

https://github.com/Southpaw-TACTIC/TACTIC/pull/1391/commits/5b3eaf7619e1fd3c9dc286fbed93ac268312de61

Hope that fixes it.


RE: TACTIC tickets on 4.8 - listy - 04-24-2020

Awesome! Thank You.
Will check it soon

Don't know why, but tactic 4.7-updates brach become tactic 4.8
This is confuses me a little.

The problem with tickets seems to be fixed!

Thank You!


RE: TACTIC tickets on 4.8 - remkonoteboom - 04-30-2020

It's confusing because it's wrong. The version 4.8 should not have been set in 4.7-updates. Thanks for reporting. Will fix soon.