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 mechanism to specify debug mode for auctionReportBuyers reporting #997

Merged
merged 3 commits into from
Feb 5, 2024

Conversation

alexmturner
Copy link
Contributor

@alexmturner alexmturner commented Jan 19, 2024

Adds a new parameter to the auctionConfig to allow the debug mode to be enabled for Private Aggregation reports sent via auctionReportBuyers. See #709 for additional context.

Adds a new parameter to the auctionConfig to allow the debug mode to be enabled for Private Aggregation reports sent via auctionReportBuyers
@alexmturner
Copy link
Contributor Author

@qingxinwu could you PTAL at this too? Thanks!

}

// Additional parameter for configuring the debug mode
'auctionReportBuyerDebugModeConfigs': [
Copy link
Collaborator

Choose a reason for hiding this comment

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

maybe add a sentence below to describe the auctionReportBuyerDebugModeConfigs field with more details, like its debugKey is optional, enabled is false if not provided, etc,.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yep, makes sense. added some more details

@alexmturner
Copy link
Contributor Author

@qingxinwu sorry for the churn, but I just realized that having a different config for each buyer doesn't really make sense. All these reports are going to the same seller, so we probably only want one config. PTAL and let me know if you think that makes sense. (Side note: I'll work to update the cl now.)

@qingxinwu
Copy link
Collaborator

@qingxinwu sorry for the churn, but I just realized that having a different config for each buyer doesn't really make sense. All these reports are going to the same seller, so we probably only want one config. PTAL and let me know if you think that makes sense. (Side note: I'll work to update the cl now.)

I think it makes sense. There's no per-buyer related information to be included in the report when debug mode is enabled, right? So that there's no need to control the config at per-buyer level?

@alexmturner
Copy link
Contributor Author

Yeah, that was my thinking too. Thanks for the re-review!

@qingxinwu
Copy link
Collaborator

may want to reference to #709 in the PR's description.

@alexmturner
Copy link
Contributor Author

Done!

aarongable pushed a commit to chromium/chromium that referenced this pull request Jan 23, 2024
Adds support for enabling the Private Aggregation debug mode for this
type of reporting. This is enabled through a new, optional field on the
auctionConfig (defaulting to debug mode disabled).

See the proposed explainer update here:
WICG/turtledove#997

This enables the new feature by default, but this feature will be
disabled before reaching Stable if it not yet approved in an I2S.

Low-Coverage-Reason: Simple mojom traits accessors
Bug: 1513013
Change-Id: I4f55b1f6d0563ab39e795a136a8b40e931e87313
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5134306
Commit-Queue: Alex Turner <[email protected]>
Reviewed-by: Dominic Farolino <[email protected]>
Reviewed-by: Qingxin Wu <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1251011}
aarongable pushed a commit to chromium/chromium that referenced this pull request Jan 24, 2024
This reverts commit 60e5bac.

Reason for revert: Causing try job failures blocking CQ:
https://ci.chromium.org/ui/p/chromium/builders/try/mac-rel/1654390/blamelist
See bug.
Bug: 1521132

Original change's description:
> Support debug mode in auctionReportBuyers reporting
>
> Adds support for enabling the Private Aggregation debug mode for this
> type of reporting. This is enabled through a new, optional field on the
> auctionConfig (defaulting to debug mode disabled).
>
> See the proposed explainer update here:
> WICG/turtledove#997
>
> This enables the new feature by default, but this feature will be
> disabled before reaching Stable if it not yet approved in an I2S.
>
> Low-Coverage-Reason: Simple mojom traits accessors
> Bug: 1513013
> Change-Id: I4f55b1f6d0563ab39e795a136a8b40e931e87313
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5134306
> Commit-Queue: Alex Turner <[email protected]>
> Reviewed-by: Dominic Farolino <[email protected]>
> Reviewed-by: Qingxin Wu <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1251011}

Bug: 1513013
Change-Id: I9c4c4a683b82bd1d2a5597e3a0881e9e095f8f19
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5232840
Bot-Commit: Rubber Stamper <[email protected]>
Owners-Override: Alan Cutter <[email protected]>
Commit-Queue: Alan Cutter <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1251216}
aarongable pushed a commit to chromium/chromium that referenced this pull request Jan 24, 2024
This is a reland of commit 60e5bac

Original change was speculatively reverted due to tryjob failures, but
another cl was the actual culprit.

Original change's description:
> Support debug mode in auctionReportBuyers reporting
>
> Adds support for enabling the Private Aggregation debug mode for this
> type of reporting. This is enabled through a new, optional field on the
> auctionConfig (defaulting to debug mode disabled).
>
> See the proposed explainer update here:
> WICG/turtledove#997
>
> This enables the new feature by default, but this feature will be
> disabled before reaching Stable if it not yet approved in an I2S.
>
> Low-Coverage-Reason: Simple mojom traits accessors
> Bug: 1513013
> Change-Id: I4f55b1f6d0563ab39e795a136a8b40e931e87313
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5134306
> Commit-Queue: Alex Turner <[email protected]>
> Reviewed-by: Dominic Farolino <[email protected]>
> Reviewed-by: Qingxin Wu <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1251011}

Bug: 1513013, 1521132
Change-Id: Id52213226117cb4179a8f38c4f4d05200d0bef57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5231585
Reviewed-by: Qingxin Wu <[email protected]>
Auto-Submit: Alex Turner <[email protected]>
Commit-Queue: Alex Turner <[email protected]>
Reviewed-by: Dominic Farolino <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1251684}
@dmdabbs
Copy link
Contributor

dmdabbs commented Jan 24, 2024

When do you expect the relanded CL to hit Canary?

@alexmturner
Copy link
Contributor Author

The relanded cl should now be available in the latest Canary (123.0.6264.0)

@qingxinwu qingxinwu merged commit 165b569 into WICG:main Feb 5, 2024
2 checks passed
github-actions bot added a commit that referenced this pull request Feb 5, 2024
…#997)

SHA: 165b569
Reason: push, by qingxinwu

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@alexmturner alexmturner deleted the patch-2 branch February 5, 2024 17:49
github-actions bot added a commit to qingxinwu/turtledove that referenced this pull request Feb 6, 2024
…WICG#997)

SHA: 165b569
Reason: push, by qingxinwu

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

None yet

3 participants