ProcessWire
ProcessWire copied to clipboard
ryancramerdesign
ProcessLogger only shows 1 message per a second
If I log things and look at log using the ProcessLogger, it only shows max 1 message per second, even if there's multiple logged in the same second. This can be very confusing and relying on that it's easy to miss important things maybe.
There is no 1-per-second max for PW's WireLog/ProcessLogger. Take a look in your system-updater log and you should see plenty of log entries with the same timestamp. I think you may be instead seeing that WireLog collapses 100% identical log entries right next to each other during the same request, so that you don't fill up your logs with useless info. PW's notices and notifications work the same way. If you want to avoid that behavior (like when debugging something), include some changing component in your log entry, like an incrementing counter or just an mt_rand() result.
I still don't like that behaviour. It's understandable for standard admin notices, but as soon as it comes to debugging it's often necessary to confirm something is called a specific number of times and I cannot imagine this to be expected by devs in any way. I'd think this is causing more confusion than it solving an issue. I'd would rather have it disabled for things like debug notices and logs or at least have it configurable.
