Currently in the process of scraping, chromedp will log various errors that don't seem to have any actual negative impact on the scraping process, i.e.:
ERROR: could not unmarshal event: unknown ClientNavigationReason value: initialFrameNavigation
and other, similar errors. These errors clutter the logs and should either be fixed or suppressed.
This issue involves performing two tasks:
[ ] Identify the cause of the errors -- particularly, whether they're due to an error on our part or a problem with chromedp itself
Currently in the process of scraping, chromedp will log various errors that don't seem to have any actual negative impact on the scraping process, i.e.:
and other, similar errors. These errors clutter the logs and should either be fixed or suppressed.
This issue involves performing two tasks: