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]: Install Broken - M1 Mac #11381

Closed
2 tasks
Bug-Reaper opened this issue Nov 14, 2023 · 3 comments
Closed
2 tasks

[Bug]: Install Broken - M1 Mac #11381

Bug-Reaper opened this issue Nov 14, 2023 · 3 comments

Comments

@Bug-Reaper
Copy link

Bug-Reaper commented Nov 14, 2023

Minimal, reproducible example

`npm i puppeteer`

Error string

npm ERR! code 1
npm ERR! path /<MyDirectoryRedacted>/
npm ERR! command failed
npm ERR! command sh -c -- node install.mjs
npm ERR! ERROR: Failed to set up Chrome r119.0.6045.105! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
npm ERR! Error: connect ETIMEDOUT 34.104.35.123:443
npm ERR!     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
npm ERR!   errno: -60,
npm ERR!   code: 'ETIMEDOUT',
npm ERR!   syscall: 'connect',
npm ERR!   address: '34.104.35.123',
npm ERR!   port: 443
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/<MyUserNameRedacted>/.npm/_logs/2023-11-14T00_27_57_330Z-debug-0.log

Bug behavior

  • Flaky
  • PDF

Background

Install Puppeteer

Expectation

Went to install the npm lib

Reality

failure to download chrome during install of npm lib

Puppeteer configuration file (if used)

No response

Puppeteer version

21.5.1

Node version

16.20.2

Package manager

npm

Package manager version

8.19.4

Operating system

macOS - Ventura 13


EDIT: Updated Puppeteer Version. It's the latest as of Nov 14th, 2023.

Copy link

github-actions bot commented Nov 14, 2023

This issue has an unsupported OS: `macos - ventura 13


edit: updated puppeteer version. it's the latest as of nov 14th, 2023.. Only the following operating systems are supported: windows ,macos ,linux`. Please verify the issue on a supported OS and update the form.


Analyzer run

@Bug-Reaper
Copy link
Author

Bug-Reaper commented Nov 14, 2023

This issue was not reproducible. Please check that your example runs locally and the following:

* Ensure the script does not rely on dependencies outside of `puppeteer` and `puppeteer-core`.

* Ensure the error string is just the error message.
  
  * Bad:
    ```ts
    Error: something went wrong
      at Object.<anonymous> (/Users/username/repository/script.js:2:1)
      at Module._compile (node:internal/modules/cjs/loader:1159:14)
      at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
      at Module.load (node:internal/modules/cjs/loader:1037:32)
      at Module._load (node:internal/modules/cjs/loader:878:12)
      at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
      at node:internal/main/run_main_module:23:47
    ```
  * Good: `Error: something went wrong`.

* Ensure your configuration file (if applicable) is valid.

* If the issue is flaky (does not reproduce all the time), make sure 'Flaky' is checked.

* If the issue is not expected to error, make sure to write 'no error'.

Once the above checks are satisfied, please edit your issue with the changes and we will try to reproduce the bug again.

Analyzer run

It is reproducible on my computer at least. It has to do with install and not runtime application so unsurprising that the automatic bug-checker fails.


Seems like it might be an outage on google's part as the remote IP address used to fetch chrome seems to not work:

http://34.104.35.123

Screenshot 2023-11-14 at 1 46 54 AM

@Bug-Reaper
Copy link
Author

Works now, gonna assume issue on google CDN side and close

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

No branches or pull requests

1 participant