Bump openssl from 0.10.59 to 0.10.60 in /tools/crates/gnrt #206
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 [openssl](https://github.com/sfackler/rust-openssl) from 0.10.59 to 0.10.60. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](sfackler/rust-openssl@openssl-v0.10.59...openssl-v0.10.60) --- updated-dependencies: - dependency-name: openssl dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
Aikoyori
pushed a commit
to Pissandshittium/pissandshittium
that referenced
this pull request
Dec 8, 2023
This CL updates the ash version ['121.0.6109.0'] for Lacros version skew testing. This cl only affect linux-lacros config builders like linux-lacros-tester-rel, linux-lacros-rel. This cl will certainly NOT affect Lacros on-device builders (lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab, etc) or any other platforms. If this CL caused regressions, please revert and stop the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org. R=rubber-stamper@appspot.gserviceaccount.com Bug: None Change-Id: Ia41e5801570316d3df79cc8a63b62da1a66244f5 Requires-Testing: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5006158 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{chromium#206} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
aarongable
pushed a commit
that referenced
this pull request
Jan 6, 2024
…1-merged This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file go/crostc-bug. Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-beta Please CC c-compiler-chrome@google.com,mobiletc-prebuild@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 Tbr: mobiletc-prebuild@google.com Change-Id: I77c75780e33c771b20585bbe06ca1d24a19b6e9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5109681 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/6167@{#206} Cr-Branched-From: 222e786-refs/heads/main@{#1233107}
aarongable
pushed a commit
that referenced
this pull request
Jan 10, 2024
This CL introduces the UserColorSource enum to the key, replacing the previous is_grayscale param in the process. The enum defines baseline, grayscale and accent color sources. These options define how the color pipeline selects the input color for the generation of sys color tokens. These options are intended to be mutually exclusive. This CL also sets the default source to baseline on windows platforms. Follow up CLs will populate the user_color on Windows' NativeTheme instance from the AccentColorObserver. However on Windows we do not want to express this accent color unless the user has explicitly opted to do so for their browser. This is in contrast to ChromeOS where we expect the accent color to be expressed in the absence of any overrides by the browser. (cherry picked from commit 74dcbb5) Bug: 1469713 Change-Id: I3c428d9d2d0f510c44decedef62c16b847ce1d1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4842769 Reviewed-by: Sean Kau <skau@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Allen Bauer <kylixrd@chromium.org> Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org> Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1193125} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4856014 Auto-Submit: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/branch-heads/5993@{#206} Cr-Branched-From: 5113507-refs/heads/main@{#1192594}
aarongable
pushed a commit
that referenced
this pull request
Jan 29, 2024
Roll Chrome Win64 PGO profile from chrome-win64-6261-1706462268-485b1b7e4831c7e96f48562fb695817e118586fd.profdata to chrome-win64-6261-1706478259-a2f733f3e583d03e0b932c6f3966becdaeb15c30.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-win64-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-m122.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I21a9fbb3bd166786018a60c7c832fa9d40db09f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5243767 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/6261@{#206} Cr-Branched-From: 9755d9d-refs/heads/main@{#1250580}
NaaeemMalik
pushed a commit
to AsilHQ/Asil-Chromium
that referenced
this pull request
Feb 8, 2024
…H swaps. When resuming a navigation that had been saved into RenderFrameHostImpl::pending_navigate_, we need to account for the fact that OnBeginNavigation() calls GetFrameHostForNavigation() which may perform an early RenderFrameHost swap and synchronously destroy the old RFH. There's also no need to keep a pending_navigate_ around after the corresponding renderer process crashes, so this CL also adds logic to clear it. Resuming such a navigation would require additional work, since the NavigationClient stashed in pending_navigate_ is no longer usable and would just immediately call the disconnect handler and cancel the navigation. But there isn't really any benefit to adding that complexity, and we already cancel the RFH's other ongoing navigations when its renderer process dies. This CL also tweaks the logic in RenderWidgetHostImpl to allow the resuming logic (ResumeLoadingCreatedWebContents) to work without hitting DCHECKs, if it's called after a renderer process crash. This case never worked cleanly before, but is supported now (and allows the new test to work without crashing). (cherry picked from commit 093daae) Bug: 1487110 Change-Id: Icd6a55002e52729e6ee966210efba1a5ce23eb55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4908270 Commit-Queue: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1205927} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4923109 Reviewed-by: Krishna Govind <govind@chromium.org> Commit-Queue: Krishna Govind <govind@chromium.org> Owners-Override: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/6045@{chromium#206} 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
If chrome.addTrustedSyncEncryptionRecoveryMethod() is invoked in incognito, it does nothing. This patch adds a metric to count how often that is the case. Strictly speaking, other than the metric itself, there is another behavioral difference: the API invocations will now complete, rather than be ignored indefinitely. This is a negligible change but, if at all, could be considered good, as it makes incognito more similar to regular profiles from the caller's point of view. (cherry picked from commit ff5e9d8) Change-Id: If667057432132394561f52b1e4229c512a33d859 Bug: 1411694 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4219114 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by: Rushan Suleymanov <rushans@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1100959} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4223194 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5563@{chromium#206} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
aarongable
pushed a commit
that referenced
this pull request
Feb 27, 2024
There has been evidence that download:decideDestinationUsingResponse:... handler can be called while there is already a _startDownloadBlock. While this cannot be reproduce, call the previous handler with nil before deleting it. (cherry picked from commit 416c247) Fixed: 325060573 Change-Id: I921429597fbe7e24f31167b7a2060e40e5a23ba7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5310017 Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Reviewed-by: Gauthier Ambard <gambard@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1263990} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5323503 Cr-Commit-Position: refs/branch-heads/6312@{#206} 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 Linux PGO profile from chrome-linux-5790-1685553847-5a1249cdcf05a56abf190afc0d8684a856df1f85.profdata to chrome-linux-5790-1685572025-6a2f8e3fe0e79c614cc2593a21521cd8f1da023c.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://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:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I6074972d2e9ab4d1a03b769e5afacb83dbd15927 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4576515 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#206} Cr-Branched-From: 1d71a33-refs/heads/main@{#1148114}
NaaeemMalik
pushed a commit
to SoftwarePrince/Egon-Chromium
that referenced
this pull request
Mar 22, 2024
…stem theme Add a toggle to choose to follow the system theme. The toggle only appears on supported platforms. Choosing any other option resets the toggle. (cherry picked from commit 3ef3849) Bug: chromium:1444588 Change-Id: I3cb578a420aacd2a179637be2e76256b56bc2437 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4754965 Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Sean Kau <skau@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1183354} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4784232 Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org> Cr-Commit-Position: refs/branch-heads/5938@{chromium#206} Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
aarongable
pushed a commit
that referenced
this pull request
Mar 25, 2024
This flag was changed in https://crrev.com/c/5237233, but missed in that CL due to concurrent editing of the file. (cherry picked from commit 53cdf72) Bug: 330202418, 329556843 Change-Id: I359eca1fe7b5802852459e23a6dc9e51954f946f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5378704 Reviewed-by: Elad Alon <eladalon@chromium.org> Commit-Queue: Elad Alon <eladalon@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1274792} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5388449 Commit-Queue: Tove Petersson <tovep@chromium.org> Reviewed-by: Tove Petersson <tovep@chromium.org> Cr-Commit-Position: refs/branch-heads/6367@{#206} Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
aarongable
pushed a commit
that referenced
this pull request
Apr 22, 2024
- Only expose the API on SecureContexts. - Only allow calling the API from potentially trustworthy HTTP/HTTPS origins. Render will verify this and throw a helpful error if on an inappropriate origin. The browser enforces this condition before binding the Mojo receiver. - Enforce in the browser-side implementation that the API only works on true HTTPS origins (without supporting loadDataWithBaseURL) by checking that the last committed origin and URL agree on scheme. (cherry picked from commit df6600d) Bug: 330151742 Change-Id: I6abde47b0cb0edfe06c0e0a2cfcb32ffb5c7a194 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5455111 Reviewed-by: Peter Beverloo <peter@chromium.org> Commit-Queue: Ashley Newson <ashleynewson@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1289369} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5463958 Auto-Submit: Ashley Newson <ashleynewson@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/branch-heads/6422@{#206} 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 openssl from 0.10.59 to 0.10.60.
Release notes
Sourced from openssl's releases.
Commits
8f4b97aMerge pull request #2104 from alex/bump-for-releasedf66283Release openssl v0.10.60 and openssl-sys v0.9.961a09dc8Merge pull request #2102 from sfackler/ex-leakb0a1da5Merge branch 'master' into ex-leakf456b60Merge pull request #2099 from alex/deprecate-store-ref-objectsa8413b8Merge pull request #2100 from alex/symm-update-uncheckeda92c237clippye839496Don't leak when overwriting ex data602d38dAddedupdate_uncheckedtosymm::Cryptercf9681afixes #2096 -- deprecateX509StoreRef::objects, it is unsoundYou can trigger a rebase of this PR 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.