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

Add Nebula support for P3A/Constellation (uplift to 1.68) #24329

Merged
merged 10 commits into from
Jun 26, 2024

Conversation

DJAndries
Copy link
Collaborator

Resolves brave/brave-browser#35841
Uplift of #22522

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • 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 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:

DJAndries and others added 10 commits June 21, 2024 15:41
Describe where the new constants come from and link to the original
issue which describes the protocol design.
Use `const` annotations for local variables that don't need
multiple assignment to make the flow contract more obvious.

Addresses a review comment.
Halt with an assert violation instead of dereferencing a null.

Addressses a review comment.
This really does two things, which I've tried to make more clear
with a comment, but `MaybeFoo` is a more common idiom in our code,
and it avoids the misleading idea that scrambling happens most of
the time.
Return early after discarding Histograms which won't be submitted
so we don't waste time trying to process them further.
@DJAndries DJAndries requested a review from a team as a code owner June 21, 2024 22:51
@kjozwiak kjozwiak added this to the 1.68.x - Beta milestone Jun 26, 2024
Copy link
Member

@kjozwiak kjozwiak left a comment

Choose a reason for hiding this comment

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

Uplift into 1.68.x approved 👍 QA has verified the PR on Nightly using 1.69.x as per #22522 (comment).

@kjozwiak kjozwiak merged commit bbae8fd into 1.68.x Jun 26, 2024
15 checks passed
@kjozwiak kjozwiak deleted the nebula-p3a-1.68.x branch June 26, 2024 21:18
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