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.










share|improve this question

























    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.










    share|improve this question























      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.










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 21:26









      user3661646

      278




      278



























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          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






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Darth Vader #20

          How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

          Ondo