@cehbrecht if I remember correctly, the new "watchdog" service have to be activated in the config so could we simply leave it there on master because it is not active by default anyways? I just don't remember if the previous mechanism it replaces is still on master or not.
But good call to go-live with one change at a time so it's easier to debug.
@tlvu the implementation for the “watchdog, job queue” has changed … also introducing database migration. Currently we don’t use the master … still relying on 4.2.x … I would feel better if we can get the master in production again … and bring in the changes one by one: py3 only, database migration, job queue ...
py3 only would be a 4.4.x release … database migration and jobqueue could go in 5.x.
@tomkralidis@ldesousa do you have opinions on “moving jobqueue to dev branch”? How would you safely revert changes on master?
sure, no objections
watchdog ... is replaced by the jobque isn't it?
and that is in master and working well afaik?
or I'm lost
“Watchdog”=jobqueue … just the name I remembered. The jobqueue is still not finalised and we don’t use the master at the moment …
well, but it is in the master afaik and the jobqueue afaik works (?(
there are still things missing (clean up of the database) and we didn’t get it into production. We are relying on the 4.2.x branch … and backporting patches from master to 4.2.x is troublesome … it has still py2 compatibility. An alternative could be to make a 4.4.x branch with py3 only support.