Skip to content

Fix missing Ethereum permissions header #17390

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

Merged

Conversation

emerick
Copy link
Contributor

@emerick emerick commented Feb 27, 2023

Resolves brave/brave-browser#28773

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally:
    • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
    • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@emerick emerick requested a review from mkarolin February 27, 2023 15:05
@emerick emerick self-assigned this Feb 27, 2023
@github-actions github-actions bot added the CI/storybook-url Deploy storybook and provide a unique URL for each build label Feb 27, 2023
@brave-builds
Copy link
Collaborator

A Storybook has been deployed to preview UI for the latest push

Copy link
Collaborator

@mkarolin mkarolin left a comment

Choose a reason for hiding this comment

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

++

@emerick emerick merged commit 2691591 into master Feb 27, 2023
@emerick emerick deleted the cr111-followup-fix-missing-ethereum-permissions-header branch February 27, 2023 19:41
@emerick emerick added this to the 1.50.x - Nightly milestone Feb 27, 2023
emerick added a commit that referenced this pull request Feb 27, 2023
…eum-permissions-header

Fix missing Ethereum permissions header
kjozwiak pushed a commit that referenced this pull request Mar 1, 2023
* Merge pull request #17033 from brave/cr111

* Partial refactor of PageGraph to use WTF types (#16953)

This is a partial refactor of PageGraph to make use of WTF types where
possible. A much larger change enforcing the use of WTF::String will be
submitted separately. The changes in this PR are aiming in making that
work easier.

Chromium change:
https://chromium.googlesource.com/chromium/src/+/52472aba170b71f97ae9ab17f429ff494537adae

commit 52472aba170b71f97ae9ab17f429ff494537adae
Author: Xianzhu Wang <[email protected]>
Date:   Mon Jan 9 20:26:58 2023 +0000

    Enable discouraged type check for data members under blink/renderer

    For existing usages of discouraged type:
    - Simple cases are changed to use blink types;
    - For other cases, ALLOW_DISCOURAGED_TYPE(reason) is added.

    Rules audit_non_blink_usages.py checking such usages are removed.
    We'll use the clang plugin from now on.

    Bug: 1363780

* Using WTF::String for blink data members (#16988)

Upstream chromium has rolled out clang checks in upcoming versions that
will error out in cases where blink headers are using `std::string` as
data member type.

This change replaces all uses of `std::string` with `WTF::String` for
data members in blink headers.

Chromium change:
https://chromium.googlesource.com/chromium/src/+/52472aba170b71f97ae9ab17f429ff494537adae

commit 52472aba170b71f97ae9ab17f429ff494537adae
Author: Xianzhu Wang <[email protected]>
Date:   Mon Jan 9 20:26:58 2023 +0000

    Enable discouraged type check for data members under blink/renderer

    For existing usages of discouraged type:
    - Simple cases are changed to use blink types;
    - For other cases, ALLOW_DISCOURAGED_TYPE(reason) is added.

    Rules audit_non_blink_usages.py checking such usages are removed.
    We'll use the clang plugin from now on.

    Bug: 1363780
    Change-Id: I808524abc06c24d8f0f9867c06f4c6597bff1889
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4130490
    Commit-Queue: Xianzhu Wang <[email protected]>
    Reviewed-by: Daniel Cheng <[email protected]>
    Reviewed-by: Chris Harrelson <[email protected]>
    Cr-Commit-Position: refs/heads/main@{#1090474}

* Merge pull request #17389 from brave/cr111-followup-fix-missing-shield-settings-header

Fix missing Shield settings header

* Merge pull request #17390 from brave/cr111-followup-fix-missing-ethereum-permissions-header

Fix missing Ethereum permissions header

* Upgrade from Chromium 111.0.5563.33 to Chromium 111.0.5563.41 (#17349)

* Upgrade from Chromium 111.0.5563.33 to Chromium 111.0.5563.41

* Upgrade patches from Chromium 111.0.5563.33 to Chromium 111.0.5563.41

* Update pins list timestamp

* Disable new DIPS-related upstream unit test

---------

Co-authored-by: brave-builds <[email protected]>

* [Android] Fix for rotation of NTP images

* Resolve rewards ANR with external wallet provider

---------

Co-authored-by: cdesouza-chromium <[email protected]>
Co-authored-by: brave-builds <[email protected]>
Co-authored-by: Artem Samoilenko <[email protected]>
Co-authored-by: deeppandya <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/storybook-url Deploy storybook and provide a unique URL for each build
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ethereum and Location content settings are missing in a site content settings
3 participants