Make sure that invalid keyboard layout value in VPD does not crash public sessions |
|
Issue descriptionWe should make sure that devices with invalid vpd do not cause crashes like the one manifested in issue 700625 There should be an automated test for this, too.
,
Mar 16 2017
Making sure that VPD entries are correct by crashing, seems like a horrible user experience. I understand writing out error logs, but crashing seems, excessive. Albert what is your opinion here?
,
Mar 16 2017
BTW, I don't think we need to ensure that 'all' VPD entries are valid. We just should make sure that if a piece of code is parsing data coming from an external source (wherever it comes from, VPD, Network, anywhere), shouldn't crash if the data isn't as expected. Our code should be more fault tolerant than that. So I would suggest adding test cases to issues we fix, not a general 'is VPD data correct' test case.
,
Mar 16 2017
Well, we can have some default here, but it will make debugging more difficult. Because we'll start getting issues like "I cannot log in". |
|
►
Sign in to add a comment |
|
Comment 1 by alemate@chromium.org
, Mar 16 2017