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)
Pending code changes (auto-populated)
Backend [ID: 1311526]
GPU [ID: 1311527]
[ID: 1223084]
[ID: 1223136]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223086]
[ID: 1223034]
[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]
This is a custom field created and used by go/roadmap. [ID: 1333341]
This is a custom field created and used by go/roadmap. [ID: 1333368]
[ID: 1223031]
Dawn
Dawn>Tint
[ID: 1253656]
Supplemental component tags only. Set main component first. [ID: 1222907]
Design doc to be reviewed. [ID: 1223032]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
View issue level access limits(Press Alt + Right arrow for more information)
Maintenance work
View staffing
Estimated effort
Description
For validation there are a number of rules that intersect that cause complex interactions around attributes and vars, especially if they are module scoped vars.
The actual IR validation implementation has implemented some of them, but not all of them/we intentionally did not implement some due to causing issues with transient states.
This is currently a bit of a mess; I need to take a step back and figure out a more holistic/high-level understanding of what the rules are, and then determine how to implement that in a uniform manner, instead of piece-mealing them in over time.