You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can usually figure out a lot about the configuration of a scraper run that errored from other anecdotal info in the error, but we should use Sentry’s breadcrumbs or contexts to be more explicit about it.
Specifically, we should make sure to include:
Timeframe (--before and --after)
Start time (of the actual run, not the timeframe being scraped)
Account name (relatively anonymized, like versionista1, versionista2, instead of e-mail)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
We can usually figure out a lot about the configuration of a scraper run that errored from other anecdotal info in the error, but we should use Sentry’s breadcrumbs or contexts to be more explicit about it.
Specifically, we should make sure to include:
--before
and--after
)versionista1
,versionista2
, instead of e-mail)We are currently on a deprecated version of the Sentry SDK (see #162). Relevant docs for it are at: https://docs.sentry.io/clients/node/
The text was updated successfully, but these errors were encountered: