Claudio DeSouza
27093680a8
This warning is being switched on in Chromium. This change fixes the places where we had failures, only marking one of them as TODO. Chromium changes: https://chromium.googlesource.com/chromium/src/+/fedf0940185080c0e9aa83b3bb9921e461a98ddb commit fedf0940185080c0e9aa83b3bb9921e461a98ddb Author: Tom Sepez <tsepez@chromium.org> Date: Wed Apr 2 14:29:32 2025 -0700 Enable unsafe buffer warnings for chromium, try #3. https://crrev.com/c/6420970 should resolve the issue with the win-chrome builder. No new unsafe issues were noted by the mega-CQ. One line change in case some untestable downstream configuration breaks with an `... is unsafe` error. Bug: 390223051 Change-Id: I3732c842c53dafb3d93c7caff3526f676b1ce5b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6423410 Mega-CQ: Tom Sepez <tsepez@chromium.org> Auto-Submit: Tom Sepez <tsepez@chromium.org> Commit-Queue: Tom Sepez <tsepez@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1441809}