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

Bump node-fetch and puppeteer in /cirq-web/cirq_ts #5998

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 4, 2023

Bumps node-fetch to 2.6.9 and updates ancestor dependency puppeteer. These dependencies need to be updated together.

Updates node-fetch from 2.6.1 to 2.6.9

Release notes

Sourced from node-fetch's releases.

v2.6.9

2.6.9 (2023-01-30)

Bug Fixes

v2.6.8

2.6.8 (2023-01-13)

Bug Fixes

v2.6.7

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.2

fixed main path in package.json

Commits
  • 70f592d fix: "global is not defined" (#1704)
  • 0f1ebb0 Prevent error when response is null (#1699)
  • 6e9464d ci(release): install dependencies
  • dd2a0ba ci(release): install dependencies
  • 49bef02 ci(release): use latest Node LTS
  • ce37bcd ci(semantic-release): config
  • 1768eaa ci(release): initial version
  • 8bb6e31 fix: prevent hoisting of the undefined global variable in browser.js (#1534)
  • e218f8d Add missing changelog entries. (#1613)
  • fddad0e fix(headers): don't forward secure headers on protocol change (#1605)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by node-fetch-bot, a new releaser for node-fetch since your current version.


Updates puppeteer from 10.0.0 to 19.6.3

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v19.6.3

19.6.3 (2023-02-01)

Bug Fixes

  • ignore not found contexts for console messages (#9595) (390685b)
  • restore WaitTask terminate condition (#9612) (e16cbc6)

puppeteer: v19.6.3

19.6.3 (2023-02-01)

Miscellaneous Chores

  • puppeteer: Synchronize puppeteer versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 19.6.2 to 19.6.3

puppeteer-core: v19.6.2

19.6.2 (2023-01-27)

Bug Fixes

puppeteer: v19.6.2

19.6.2 (2023-01-27)

Miscellaneous Chores

  • puppeteer: Synchronize puppeteer versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 19.6.1 to 19.6.2

puppeteer-core: v19.6.1

19.6.1 (2023-01-26)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for puppeteer since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [node-fetch](https://github.com/node-fetch/node-fetch) to 2.6.9 and updates ancestor dependency [puppeteer](https://github.com/puppeteer/puppeteer). These dependencies need to be updated together.


Updates `node-fetch` from 2.6.1 to 2.6.9
- [Release notes](https://github.com/node-fetch/node-fetch/releases)
- [Commits](node-fetch/node-fetch@v2.6.1...v2.6.9)

Updates `puppeteer` from 10.0.0 to 19.6.3
- [Release notes](https://github.com/puppeteer/puppeteer/releases)
- [Changelog](https://github.com/puppeteer/puppeteer/blob/main/release-please-config.json)
- [Commits](puppeteer/puppeteer@v10.0.0...puppeteer-v19.6.3)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
- dependency-name: puppeteer
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested review from a team, vtomole and cduck as code owners February 4, 2023 10:43
@dependabot dependabot bot requested a review from verult February 4, 2023 10:43
@dependabot dependabot bot added dependencies area/javascript Pull requests that update Javascript code labels Feb 4, 2023
@pavoljuhas
Copy link
Collaborator

@seunomonije - I hope all is going great, would you mind taking a quick look?
Perhaps the failing CI test has an obvious fix from your POV. Thank you!

@pavoljuhas pavoljuhas requested a review from wcourtney February 8, 2023 23:54
@CirqBot CirqBot added the size: L 250< lines changed <1000 label Feb 12, 2023
@pavoljuhas
Copy link
Collaborator

Thanks to wcourtney for updating expected PNGs. The tests are passing locally on Debian-like OS, but failing on GHA.
Any tips how to resolve this?

@senecameeks
Copy link
Collaborator

I can take a look, sometimes chrome updates can cause matchers to fail and you have to use another matcher that is compatible with the new update.

@pavoljuhas
Copy link
Collaborator

Thank you @senecameeks for helping with this, let me know if you have any questions.

@pavoljuhas
Copy link
Collaborator

@senecameeks - there is a related PR #6014; it seems that ci.yml was missing - actions/setup-node.
Here we also upgrade the puppeteer so that may be another source for failing CI.

@vtomole
Copy link
Collaborator

vtomole commented Feb 21, 2023

@pavoljuhas Changed to v2 and it's still failing.

@pavoljuhas
Copy link
Collaborator

Changed to v2 and it's still failing.

the test is passing on my debian box with identical PNGs.
Seems that GH environment has a slightly different rendering.
Should we try to revert 5599798?

@senecameeks
Copy link
Collaborator

If reverting doesn't work, we can try treating the pngs as binary files (https://blog.jongallant.com/2021/02/png-files-not-rendering-on-github/)

Adding
.png binary to .gitattributes

I haven't gotten the tests to run properly on my workstation if someone wants to quickly test this idea out.

pavoljuhas and others added 5 commits February 22, 2023 15:00
Check if original expected PNGs would work on GHA.

This reverts commit 5599798.
No joy - back to the updated PNGs.

This reverts commit 4cf21fd.
… local run I can see that that the diff comes from the black/dark gray pixels.
senecameeks and others added 2 commits March 3, 2023 09:21
… text symbols had been slightly darker and more bold (from a chrome update I suspect) causing the pixelmatcher to fail. This now passes locally on my macOS.
…-puppeteer-2.6.9' of github.com:quantumlib/cirq into dependabot/npm_and_yarn/cirq-web/cirq_ts/node-fetch-and-puppeteer-2.6.9
@senecameeks
Copy link
Collaborator

Updated the expected images so now the tests are passing. Cleaning up the commits so we can merge.

@pavoljuhas
Copy link
Collaborator

Looks great, thank you for taking care of this!

@senecameeks senecameeks merged commit 8b97aa5 into master Mar 7, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/cirq-web/cirq_ts/node-fetch-and-puppeteer-2.6.9 branch March 7, 2023 01:48
@vtomole
Copy link
Collaborator

vtomole commented Mar 7, 2023

Thank you so much @senecameeks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies area/javascript Pull requests that update Javascript code size: L 250< lines changed <1000
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants