-
Notifications
You must be signed in to change notification settings - Fork 0
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
pyppeteer is having problems launching or otherwise processing the hitlist #39
Comments
I believe part of this bug was that the check for Burp Suite's proxy being up/running was not very robust. The proxy (i.e. Anyway... there's still something going on here. Further debug is needed before issue can be closed. |
pyppeteer was working before for sure. It would print stuff to the console and whatever. Now there is some issue. A pull request out there for it suggests maybe an issue on Windows. Need to dig in, look at pyppeteer's logging, etc. |
Haven't done the above but seems that pyppeteer may be dead, at its official repo. There are some forks farther ahead and this one looks promising - https://github.com/CircleOnCircles/pyppeteer/tree/dev-wackazong |
From doing
|
I cleared the local Chromium that pyppeteer had downloaded, didn't make a difference. However, I was able to successfully run the test script below. So somewhere along the way of me writing this tool the calls to pyppeteer went sideways. Probably easiest thing to do is try to get main script closer to this test script and consider the discrepancy. import asyncio
from pyppeteer import launch
async def main():
browser = await launch()
page = await browser.newPage()
await page.goto('http://example.com')
await page.screenshot({'path': 'example.png'})
await browser.close()
asyncio.get_event_loop().run_until_complete(main()) |
Figured out what the problem is and opened #47 to deal with it. For now the check of whether Burp Suite is up has been hard-coded |
Hitlist processing hangs forever if Burp isn't up on the expected proxy port
The text was updated successfully, but these errors were encountered: