Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: OCE performance scan failing upon hitting 10x.gsa.gov #127

Open
maomeara63 opened this issue Mar 20, 2024 · 1 comment
Open

Bug: OCE performance scan failing upon hitting 10x.gsa.gov #127

maomeara63 opened this issue Mar 20, 2024 · 1 comment
Assignees

Comments

@maomeara63
Copy link
Contributor

maomeara63 commented Mar 20, 2024

Who discovered this?

Jonah Hatfield

What happened?

10x site is throwing a weird error when we try to crawl the site for the 9 performance metrics GSA reports to OMB every quarter. The error stops the crawling script, forcing [@Jonah Hatfield - IR](mailto:jonah.hatfield@gsa.gov) to manually eliminate it from the list in order to continue. The error is: "Error: Node is either not clickable or not an HTMLElement"

What pages did this appear on?

No response

Detail the steps for someone to reproduce

No response

What browsers are you seeing the problem on?

No response

Relevant log output

No response

@jonadecker
Copy link
Contributor

Looks like a Puppeteer issue, either not waiting for the DOM to completely finish loading, or looking for a selector that doesn't exist.

https://stackoverflow.com/questions/51857070/puppeteer-in-nodejs-reports-error-node-is-either-not-visible-or-not-an-htmlele
https://stackoverflow.com/a/70894113

Maybe using JS click HTMLElement.click() vs. Puppeteer's button click ElementHandle.click() but can't rule out Puppeteer looking for a selector that doesn't exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants