Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Show all 161 items in the list
Show all 15 items in the list
Pending code changes (auto-populated)
[ID: 1223031]
Internals>Core
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Internals
[ID: 1253656]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Estimated effort
Description
#1Plan for progress here:
- Rewrite base APIs and their users and base implementations to use span.
- At some point start to verify that some parts of //base can be built with -Wunsafe-buffer-usage
- To do that we can pull some .cc files out of base into a source_set and apply the warning to them.
- This will show how to prevent backsliding, and we can do this until all of //base cc files pass, and apply the warning to base but not to things that depend on it yet (in GN configs but not all_dependent_configs)