There seems to be a bug when calculating the idle time. From skimming the code it seems that intervention should should itself down when the idle time of the machine is > 90 seconds I guess?
Running on osx this doesn't seem to work, when invoked by the cronjob it still gives me the intervention screen and in fact will run multiple instances at the same time. So when returning to my machine after 45 minutes I might have 3 intervention windows open at the same time. Did you experience something similar on your end?
There seems to be a bug when calculating the idle time. From skimming the code it seems that intervention should should itself down when the idle time of the machine is > 90 seconds I guess?
Running on osx this doesn't seem to work, when invoked by the cronjob it still gives me the intervention screen and in fact will run multiple instances at the same time. So when returning to my machine after 45 minutes I might have 3 intervention windows open at the same time. Did you experience something similar on your end?