Extensions: warn not fail on UnknownError during signature verification #169777
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.
Resolve #164726.
This change does a few things:
Re-enables extension signature verification on Linux armhf.
Logs a warning (not an error) if extension signature verification fails with
UnknownError
.Example of verification success:
Example of verification failure with
UnknownError
:Allows an extension install/update to proceed if extension signature verification failed with
UnknownError
.Reports via telemetry if extension signature verification failed with
UnknownError
.Note that this PR does not fix the underlying problem (TBD) causing
UnknownError
.CC @isidorn, @sandy081, @joaomoreno