- Oct 19, 2023
-
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
* For >=5.68, we expect 'civicrm_queue.runner' to be deprecated. * For >=5.68, we should use 'civicrm_queue.agent' instead * For <5.68, we must still use 'civicrm_queue.runner' * This also allows admins to improvise on queries
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
totten authored
-
- Jul 03, 2023
-
- Dec 08, 2022
-
-
Eileen McNaughton authored
-
- Nov 03, 2022
-
-
totten authored
-
- Oct 27, 2022
- Oct 26, 2022
-
-
totten authored
-
totten authored
-
totten authored
* At NOTICE level, you should see 1-2 messages whenever there's an actual task to work on * At INFO level (`-v`), you should see setup/teardown records for each major component (control channel, pool, pool-members) * At DEBUG level (`-vv`), you should see detailed I/O
-