Bump h2 from 0.3.22 to 0.3.24 in /tools/crates/gnrt #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [h2](https://github.com/hyperium/h2) from 0.3.22 to 0.3.24. - [Release notes](https://github.com/hyperium/h2/releases) - [Changelog](https://github.com/hyperium/h2/blob/v0.3.24/CHANGELOG.md) - [Commits](hyperium/h2@v0.3.22...v0.3.24) --- updated-dependencies: - dependency-name: h2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
aarongable
pushed a commit
that referenced
this pull request
Jan 19, 2024
Roll Chrome Linux PGO profile from chrome-linux-6099-1699220220-8315e835e9264016d8d2c442a097ffa82f2db1e9.profdata to chrome-linux-6099-1699241318-5a3b3404dca17e0877136f36c818e070fd5b2b6f.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I6ed5f8ddcd6d166f3ba6ccd2dabde7671ac57f2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5007185 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#213} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
aarongable
pushed a commit
that referenced
this pull request
Jan 20, 2024
Automatic update for 2023-12-11 UTC Change-Id: I540aac5cfc134c76ff2e743d15bdd9c2be0361d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5110280 Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Cr-Commit-Position: refs/branch-heads/6167@{#213} Cr-Branched-From: 222e786-refs/heads/main@{#1233107}
aarongable
pushed a commit
that referenced
this pull request
Jan 20, 2024
The timestamp no longer resets to zero if the fragment was set. OBSOLETE_HISTOGRAMS[PasswordManager.PasswordMigrationWarning.EmptySheetTrigger]=Replaced by PasswordManager.PasswordMigrationWarning.EmptySheetTrigger2 (cherry picked from commit e12074a) Bug: 1480977 Change-Id: Ied2763eabdf677628db0c24901d3be9c6b585ce7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4853690 Reviewed-by: Ioana Pandele <ioanap@chromium.org> Commit-Queue: Ivana Žužić <izuzic@google.com> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Original-Commit-Position: refs/heads/main@{#1194863} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4854140 Cr-Commit-Position: refs/branch-heads/5993@{#213} Cr-Branched-From: 5113507-refs/heads/main@{#1192594}
aarongable
pushed a commit
that referenced
this pull request
Jan 26, 2024
…114.0.5735.13-r1 to 114-5735.6-1682938968-benchmark-114.0.5735.16-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I2fc64ce58891a4c70a5cc079bcb930c89c9cd590 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4503160 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5735@{#213} Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
aarongable
pushed a commit
that referenced
this pull request
Jan 29, 2024
Sometimes, when we match Mac system UI font by italic traits and then adjust weight and width variations [0], we end up getting a CTFont which has a correct `wght` variation axis value, but it's trait value is not updated. This behaviour was only observed for Mac's system UI font of size 14px, see [1] or for the same Mac system UI font in the smaller sizes (i.e. <8px), compare [2]. This CL proposes a workaround solution that adds bold trait if requested, in addition to italic trait, during system UI font matching. [0] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/fonts/mac/font_matcher_mac.mm?q=MatchSystemUIFont [1] https://crbug.com/1520661 [2] https://crbug.com/1516731 (cherry picked from commit 39e266d) Bug: 1516731 Change-Id: Id375df428de5de242d5dcca48aed6c71863298af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5224989 Commit-Queue: Munira Tursunova <moonira@google.com> Reviewed-by: Dominik Röttsches <drott@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1252037} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5238085 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/branch-heads/6261@{#213} Cr-Branched-From: 9755d9d-refs/heads/main@{#1250580}
NaaeemMalik
pushed a commit
to AsilHQ/Asil-Chromium
that referenced
this pull request
Feb 8, 2024
Roll Chrome Mac PGO profile from chrome-mac-6045-1696852631-9e671182cdadb9fa18287de51750f52b28a59d53.profdata to chrome-mac-6045-1696865868-be499a59bd15823e07f9ef956362fd88f3fd76d9.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m119.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ice2f39871a030528af6cdafdb693737c73e6047b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4922907 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6045@{chromium#213} Cr-Branched-From: 905e8bd-refs/heads/main@{#1204232}
ecotopian
pushed a commit
to ecosia/chromium-android-browser
that referenced
this pull request
Feb 12, 2024
This is a reland of commit ee2a607 The difference between this reland and the original upload is in Patchsets 3-4, which set a default value for the PendingCheck field mechanism_experiment_cache_selection because there is a second constructor that does not pass through a value for it. The change includes refactoring some common code out of V4GetHashProtocolManagerTest so that V4LocalDatabaseManagerTest can reuse it. Original change's description: > Maintain 3 separate HPD caches for the HPRT experiment > > Hash-prefix real-time checks and URL real-time checks can both fall back > to the hash-prefix database check (HPD). As such, we don't want the > different mechanisms to share the same HPD cache, to avoid one mechanism > benefitting from cached results of another mechanism's lookup. > > The two backgrounded mechanisms (hash real-time and hash database > lookups) each have their own HPD cache within V4GetHashProtocolManager. > URL real-time lookups use the primary cache as normal, since the > experiment is performed by intercepting URL real-time lookups. > > Within the context of the experiment, reads and writes are performed on > the specific mechanism's HPD cache. > Outside the context of the experiment, reads are performed only on the > primary cache. Writes are performed on all 3 of the caches. This is > because many cache updates are outside the scope of the experiment (e.g. > non-mainframe URLs, checks to non-browsing threat types), but the > backgrounded mechanisms should be allowed to reuse these results if they > happen to match, since that's how it would work if that mechanism were > the default mechanism being used. > > We only want to maintain the separate caches if the experiment might run > for the user (they are an ESB user and the feature flag is enabled). As > an approximation to keep the code simple, we start maintaining separate > caches any time there is a lookup performed where these criteria are > matched. The edge cases this misses (e.g. a user enables ESB) are rare > enough that the approximation will have a negligible impact on the > results. > > Implementation details: > - V4GetHashProtocolManager has most of the changes. It holds the 3 > caches and owns the read/write logic for them. It also has the property > is_lookup_mechanism_experiment_enabled_ that determines whether it > should maintain 3 caches instead of just one. > - A MechanismExperimentHashDatabaseCache enum value is threaded through > from consumers to V4GetHashProtocolManager to specify which caches > should be used for reads/writes. Within the experiment, this says to > read/write to the specific mechanism's cache. Outside the experiment, > this specifies to read only from the primary cache and write to all 3 > caches. > - If the experiment should be enabled, at the start of a lookup, > SafeBrowsingUrlCheckerImpl kicks off a chain of > SetLookupMechanismExperimentIsEnabled calls that eventually set > is_lookup_mechanism_experiment_enabled_ to true in > V4GetHashProtocolManager. > > Bug: 1392144 > > Change-Id: Ic7aaa65d990003e6aff2420a03f125496b0d4217 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4203687 > Commit-Queue: thefrog <thefrog@chromium.org> > Reviewed-by: Xinghui Lu <xinghuilu@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1100477} (cherry picked from commit 7c7c040) Bug: 1392144 Change-Id: I911b854c157092630c6c809b4f4fdf3719e6b686 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4220115 Commit-Queue: thefrog <thefrog@chromium.org> Reviewed-by: Xinghui Lu <xinghuilu@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1101166} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4226193 Cr-Commit-Position: refs/branch-heads/5563@{chromium#213} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
aarongable
pushed a commit
that referenced
this pull request
Feb 27, 2024
Automatic update for 2024-02-27 UTC Change-Id: I614b979be4649420972648f64a88147b728b5cf4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5324914 Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Cr-Commit-Position: refs/branch-heads/6312@{#213} Cr-Branched-From: 6711dcd-refs/heads/main@{#1262506}
gcjenkinson
pushed a commit
to chromium-cheri/chromium
that referenced
this pull request
Mar 15, 2024
Roll Chrome Mac PGO profile from chrome-mac-5790-1685572025-44beed08240497f5c826a52e5ac52d3f05934500.profdata to chrome-mac-5790-1685595566-526ca4fed35f6a17be852abb5bb2eed8b04fb928.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m115.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I3ec2bdf0faf151d93f7a9a809bde948c31ba6c24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4578799 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5790@{chromium#213} Cr-Branched-From: 1d71a33-refs/heads/main@{#1148114}
NaaeemMalik
pushed a commit
to SoftwarePrince/Egon-Chromium
that referenced
this pull request
Mar 22, 2024
Change-Id: I5278bfde0206be1b08db336b56f547e36927f1f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4788187 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5938@{chromium#213} Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
aarongable
pushed a commit
that referenced
this pull request
Mar 25, 2024
This reverts commit 9b92b3d. Reason for revert: This CL breaks the timer. Original change's description: > camera: Move taking state back after preparation > > This CL catches an error when a video recording is stopped before the > video recording is started. In some devices(i.e. kukui), stopping > a video recording is finished earlier than starting a recording when the > shutter is clicked so fast by pressing a space bar for long. By moving > the taking state back after the taking preparation, we can prevent the > race condition of stop operation is finished during taking preparation. > > BUG=b:328711730 > Test=By pressing a space bar in kukui/volteer > > Change-Id: Iafdf1d0f00975581188217ebc278459d78141569 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5369602 > Commit-Queue: Dorah Kim <dorahkim@google.com> > Reviewed-by: Chu-Hsuan Yang <chuhsuan@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1273983} (cherry picked from commit 76dcad7) Bug: b:328711730 Change-Id: I800e709997d7a8ae3751cdcad15fbdf7883ba38c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5387895 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Dorah Kim <dorahkim@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1276817} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5386557 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Dorah Kim <dorahkim@google.com> Cr-Commit-Position: refs/branch-heads/6367@{#213} Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
aarongable
pushed a commit
that referenced
this pull request
Apr 22, 2024
Let's have some UMA here that will make it easy to detect issues in the future. The failure rate should always be pretty low, so this might be easy to set an alert on. (cherry picked from commit 53929ab) Bug: 335705742 Change-Id: Id211fd4e524a708af425c20cda36c90dd7aa6a05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5467428 Auto-Submit: Ari Chivukula <arichiv@chromium.org> Commit-Queue: Ari Chivukula <arichiv@chromium.org> Reviewed-by: Steven Bingler <bingler@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1290074} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5462875 Commit-Queue: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/6422@{#213} Cr-Branched-From: 9012208-refs/heads/main@{#1287751}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps h2 from 0.3.22 to 0.3.24.
Release notes
Sourced from h2's releases.
Changelog
Sourced from h2's changelog.
Commits
7243ab5Prepare v0.3.24d919cd6streams: limit error resets for misbehaving connectionsa7eb14av0.3.23b668c7ffix: streams awaiting capacity lockout (#730) (#734)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.