Caleb Burks

Items 1 & 2 from above are resolved in https://github.com/Automattic/Cron-Control/pull/245. Supporting schema changes can be dealt with when the time comes for them.

New item fresh off the press: need to actively set the charset for the table upon creation, like this: https://github.com/WordPress/WordPress/blob/69e9e78cf4b63931a3d81e7ecb3c2a0cda7a13ed/wp-admin/includes/schema.php#L64

> When checking if events are firing Any context on this? Not sure I follow.

I'm thinking probably both for multisites. A site option (network-level) can exist to disable the runner network-wide. If set, `wp cron-control orchestrate runner-only get-info` will first return that it's disabled...

Cleaning up duplicate recurring events now on the daily cronjob, so that's good. Next steps I'm thinking: 1) When we determine an event doesn't exist yet (performantly), do another query...

+1, will revisit this "soon" hopefully. Right now the only way for remote alerting is via the REST API's getEvents endpoint but you have to parse through all events. We...

Documenting some of the edge-case behaviors: ``` ## Non-existing keys $flags = false; $value = $memcache->get( KEY_THAT_DOES_NOT_EXIST, $flags ); var_dump( $flags, $value ); > bool(false) bool(false) $flags = false; $value...

- Added logging so we can better track how often inconsistencies occurs. - Handled the `NULL` edge case for backwards-compatibility. - `get_multi()` didn't have a very accurate implementation for `$found`....

I am a little worried about this causing confusion for new customers, wherein they were actually relying on having node_modules committed.

I like the idea of adding to the readme. My main concern here is how the issues that typically stem from this type of thing are very hidden and hard...