Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import Firefox 66 beta3 schema. #2419

Merged
merged 1 commit into from
Feb 4, 2019
Merged

Conversation

EnTeQuAk
Copy link
Contributor

Fixes #2418

@EnTeQuAk EnTeQuAk requested a review from rpl January 31, 2019 14:07
Copy link
Member

@rpl rpl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @EnTeQuAk, the update looks good and consistent with changes we applied on mozilla-central during the 66 cycle, there are only two details that worth a mention from my point of view:

Do you mind to rerun the appveyor job? just to double-check that the failure is intermittent and not consistently reproduced.

@@ -104,7 +104,7 @@
"enum": [
"spanning"
],
"onError": "warn"
"default": "spanning"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just as a side note, this change means that extensions with "not_allowed" or "split" as the requested incognito mode will start to get errors when submitted on AMO.

The error message we currently report for this validation error is unfortunately not super useful, as it doesn't currently say which are the allowed values (currently just "spanning"):

Code           Message                           Description                           File   Line   Column
JSON_INVALID   "/incognito" should be equal to   Your JSON file could not be parsed.
               one of the allowed values

Shane checked with Mike how many of such extension we have, and they should be very few (I recall there were less then 10).

Anyway, Firefox will also raise an error an refuse to install the extension, and so the linter and AMO behavior is going to be consistent with Firefox.

@wagnerand
Copy link
Member

That test is flaky, I have seen it failing before. Restarting should fix it.

@rpl
Copy link
Member

rpl commented Jan 31, 2019

That test is flaky, I have seen it failing before. Restarting should fix it.

@wagnerand good, that's what I suspected, thanks for confirming it!
do you know if it is flaky only on appveyor or also on travis?

@wagnerand
Copy link
Member

I don't remember exactly, sorry.

@EnTeQuAk EnTeQuAk merged commit 098c55d into master Feb 4, 2019
@EnTeQuAk EnTeQuAk deleted the 2418-import-firefox-66-beta branch February 4, 2019 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants