-
Notifications
You must be signed in to change notification settings - Fork 6
Make timeout errors more understandable inside workers #465
Conversation
status.info( | ||
'🍿', | ||
wasCachedAlready | ||
? `Refetched action ID ${actionId} (team ID ${teamId}) from DB` | ||
: `Fetched new action ID ${actionId} (team ID ${teamId}) from DB` | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should leave this in, but at a reduced debug
level, which would only be shown with LogLevel.Debug
so that normally there's no spam
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, involves adding debug to status, so I'll pull it out into a separate PR instead.
PostHog/plugin-server#465) * add caller to async function guard * add simple test * add transforms test
Changes
Add a caller parameter to async guard
This will soon help make it easier to understand what's going on with errors like these: https://sentry.io/organizations/posthog/issues/2358370433/?project=5592816
... and what went wrong with Bigquery in PostHog/bigquery-plugin#9
Checklist