pyppeteer (+ asyncio) not playing nicely on AWS Severless
up vote
0
down vote
favorite
I'm trying to set up an AWS Lambda handler that involves using pyppeteer (the python-port of headless Chrome in node.js) to take a screenshot.
def getSavePath():
path = "picture_{}.png".format(random.randint(100, 1000))
loop = asyncio.get_event_loop()
loop.run_until_complete(._screenshot(path))
print("Done taking screenshot...")
return path
async def _screenshot(path):
browser = await launch()
page = await browser.newPage()
await page.goto(URL, {"waitUntil": "networkidle0"})
textBox = await page.querySelector('[name="section"]')
submitButton = await page.querySelector('#submit')
canvas = await page.querySelector("#canvas")
await textBox.click({"clickCount": 3});
await textBox.type(self.wkt)
await submitButton.click()
await canvas.screenshot({'path': path})
await browser.close()
When I run this locally, the screenshot gets taken and the path gets returned correctly.
When I run this on AWS Lambda, I'm getting:
loop.run_until_complete(._screenshot(path))
File "/var/task/asyncio/base_events.py", line 296, in run_until_complete
future = tasks.async(future, loop=self)
File "/var/task/asyncio/tasks.py", line 516, in async
raise TypeError('A Future or coroutine is required')
TypeError: A Future or coroutine is required
/var/task/slash.py:50: RuntimeWarning: coroutine '_screenshot' was never awaited
Any thoughts on why this would work locally but not on Lambda?
I'm using Python version 3.6 both locally and on Lambda.
amazon-web-services python-asyncio puppeteer
add a comment |
up vote
0
down vote
favorite
I'm trying to set up an AWS Lambda handler that involves using pyppeteer (the python-port of headless Chrome in node.js) to take a screenshot.
def getSavePath():
path = "picture_{}.png".format(random.randint(100, 1000))
loop = asyncio.get_event_loop()
loop.run_until_complete(._screenshot(path))
print("Done taking screenshot...")
return path
async def _screenshot(path):
browser = await launch()
page = await browser.newPage()
await page.goto(URL, {"waitUntil": "networkidle0"})
textBox = await page.querySelector('[name="section"]')
submitButton = await page.querySelector('#submit')
canvas = await page.querySelector("#canvas")
await textBox.click({"clickCount": 3});
await textBox.type(self.wkt)
await submitButton.click()
await canvas.screenshot({'path': path})
await browser.close()
When I run this locally, the screenshot gets taken and the path gets returned correctly.
When I run this on AWS Lambda, I'm getting:
loop.run_until_complete(._screenshot(path))
File "/var/task/asyncio/base_events.py", line 296, in run_until_complete
future = tasks.async(future, loop=self)
File "/var/task/asyncio/tasks.py", line 516, in async
raise TypeError('A Future or coroutine is required')
TypeError: A Future or coroutine is required
/var/task/slash.py:50: RuntimeWarning: coroutine '_screenshot' was never awaited
Any thoughts on why this would work locally but not on Lambda?
I'm using Python version 3.6 both locally and on Lambda.
amazon-web-services python-asyncio puppeteer
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to set up an AWS Lambda handler that involves using pyppeteer (the python-port of headless Chrome in node.js) to take a screenshot.
def getSavePath():
path = "picture_{}.png".format(random.randint(100, 1000))
loop = asyncio.get_event_loop()
loop.run_until_complete(._screenshot(path))
print("Done taking screenshot...")
return path
async def _screenshot(path):
browser = await launch()
page = await browser.newPage()
await page.goto(URL, {"waitUntil": "networkidle0"})
textBox = await page.querySelector('[name="section"]')
submitButton = await page.querySelector('#submit')
canvas = await page.querySelector("#canvas")
await textBox.click({"clickCount": 3});
await textBox.type(self.wkt)
await submitButton.click()
await canvas.screenshot({'path': path})
await browser.close()
When I run this locally, the screenshot gets taken and the path gets returned correctly.
When I run this on AWS Lambda, I'm getting:
loop.run_until_complete(._screenshot(path))
File "/var/task/asyncio/base_events.py", line 296, in run_until_complete
future = tasks.async(future, loop=self)
File "/var/task/asyncio/tasks.py", line 516, in async
raise TypeError('A Future or coroutine is required')
TypeError: A Future or coroutine is required
/var/task/slash.py:50: RuntimeWarning: coroutine '_screenshot' was never awaited
Any thoughts on why this would work locally but not on Lambda?
I'm using Python version 3.6 both locally and on Lambda.
amazon-web-services python-asyncio puppeteer
I'm trying to set up an AWS Lambda handler that involves using pyppeteer (the python-port of headless Chrome in node.js) to take a screenshot.
def getSavePath():
path = "picture_{}.png".format(random.randint(100, 1000))
loop = asyncio.get_event_loop()
loop.run_until_complete(._screenshot(path))
print("Done taking screenshot...")
return path
async def _screenshot(path):
browser = await launch()
page = await browser.newPage()
await page.goto(URL, {"waitUntil": "networkidle0"})
textBox = await page.querySelector('[name="section"]')
submitButton = await page.querySelector('#submit')
canvas = await page.querySelector("#canvas")
await textBox.click({"clickCount": 3});
await textBox.type(self.wkt)
await submitButton.click()
await canvas.screenshot({'path': path})
await browser.close()
When I run this locally, the screenshot gets taken and the path gets returned correctly.
When I run this on AWS Lambda, I'm getting:
loop.run_until_complete(._screenshot(path))
File "/var/task/asyncio/base_events.py", line 296, in run_until_complete
future = tasks.async(future, loop=self)
File "/var/task/asyncio/tasks.py", line 516, in async
raise TypeError('A Future or coroutine is required')
TypeError: A Future or coroutine is required
/var/task/slash.py:50: RuntimeWarning: coroutine '_screenshot' was never awaited
Any thoughts on why this would work locally but not on Lambda?
I'm using Python version 3.6 both locally and on Lambda.
amazon-web-services python-asyncio puppeteer
amazon-web-services python-asyncio puppeteer
asked Nov 10 at 21:26
user3661646
278
278
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53243573%2fpyppeteer-asyncio-not-playing-nicely-on-aws-severless%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown