Logs out of order
I'm seeing at least two cases where this is happening:
1. Cached response - the timestamp is older than when the response actually occurred, but it seems to be the timestamp is actually from when the cached response was originally served, which is useful info, but the actual served timestamp would be more useful.
2. Not sure what causes this, but here's an example case:
- An action logs something
- The action then calls a mutation
- The mutation throws
- In convex logs, I see the error from the mutation before the log
- The timestamp from the log is one second before the mutation error
- Timestamp is correct, order is not
I'm guessing logging isn't guaranteed to be in order, but wondering if it's a bug, or if there's any way to help improve output from my end.
1. Cached response - the timestamp is older than when the response actually occurred, but it seems to be the timestamp is actually from when the cached response was originally served, which is useful info, but the actual served timestamp would be more useful.
2. Not sure what causes this, but here's an example case:
- An action logs something
- The action then calls a mutation
- The mutation throws
- In convex logs, I see the error from the mutation before the log
- The timestamp from the log is one second before the mutation error
- Timestamp is correct, order is not
I'm guessing logging isn't guaranteed to be in order, but wondering if it's a bug, or if there's any way to help improve output from my end.
