AsamK 8f51bdcb78 Adapt maxInstancesForQueue to only consider instances of the same job. ... Currently the maxInstancesForQueue limit checks the count of all jobs in a given queue. If there are already too many jobs, the new job is discarded. However this is not the expected behavior for the two jobs where it's used: GroupCallPeekWorkerJob and AutomaticSessionResetJob For both the expected behavior is that there aren't too many jobs of them started, but that there will be at least one instance of them started. Both of them use the same queue as the PushProcessMessageJob and the MarkerJob. Those two jobs are often in the queue at the same time, effectively preventing the GroupCallPeekWorkerJob and AutomaticSessionResetJob from being enqueued.		2021-02-08 14:26:59 -05:00
..
java/org/thoughtcrime/securesms	Adapt maxInstancesForQueue to only consider instances of the same job.	2021-02-08 14:26:59 -05:00
resources	Implement new workflow for scoped storage backup selection.	2020-10-15 16:19:17 -04:00