This issue applies to both the generic Server error log as well as the Payment provider log. I claim this is a nasty bug.
My problem is that a series of quickly happening related log entries are not displayed in correct chronological order if they occurred within the same second. This makes it extremely difficult for my non-tech savvy clients to comprehend the order of events when things go wrong...Telling them that the computer is too stupid to order things properly does not make me look like a rock star.
Often (mostly, but not always? I am not really sure) they appear to be displayed in reverse chronological order - the last entry is display first & the first entry is displayed last. I could be wrong...
A quick check of the underlying table xf_error_log indicates there is an exception_date field which seems to have seconds granularity. Seconds granularity is insufficient for proper ordering of events. Thousands of things can happen each second...
My problem is that a series of quickly happening related log entries are not displayed in correct chronological order if they occurred within the same second. This makes it extremely difficult for my non-tech savvy clients to comprehend the order of events when things go wrong...Telling them that the computer is too stupid to order things properly does not make me look like a rock star.
Often (mostly, but not always? I am not really sure) they appear to be displayed in reverse chronological order - the last entry is display first & the first entry is displayed last. I could be wrong...
A quick check of the underlying table xf_error_log indicates there is an exception_date field which seems to have seconds granularity. Seconds granularity is insufficient for proper ordering of events. Thousands of things can happen each second...