Marco Lüthy
Marco Lüthy
Hi @pklingem where are you getting that error? In AWS CloudWatch or from Node in a terminal?
@pklingem was this issue resolved by v1.3.0?
Hi @wmdmark — Outside of the Lambda context, the `--disable-gpu` is not set. However, currently within the Lambda contexts, `--disable-gpu` is required or Chrome won't run correctly. This may be...
Hi @nano2K would you be able to resolve the merge conflicts on this PR?
@dunecatnat which version of Chrome are you using?
@timbaileyjones no progress. See if [puppeteer](https://github.com/GoogleChrome/puppeteer) addresses your needs. You can run puppeteer together with [serverless-chrome](https://github.com/adieuadieu/serverless-chrome). [Here](https://nadeesha.github.io/headless-chrome-puppeteer-lambda-servelerless/) is an article describing how.
@gorangajic Thank you for this PR. Would you mind adding `chromePath` while you're at it? See #184
@pklingem D'oh. You're absolutely right. Quickest solution I can think of is to simply scope the IoT topic to include the stage, e.g. `prod/chrome/new-session`. Might be able as use-case for...
Hi @stevenfitzpatrick Hm.. To help debug this, let's confirm that the session Lambda handler is working correctly. Could you try the `curl` command I describe in https://github.com/graphcool/chromeless/issues/58#issuecomment-318603329 and share all...
@stevenfitzpatrick yes that's correct—`GET /dev` endpoint is the new-session endpoint. I'll clarify that in the documentation.