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

Fix reporting's return value handling. #642

Merged
merged 11 commits into from
Jun 22, 2023
Merged

Conversation

qingxinwu
Copy link
Collaborator

@qingxinwu qingxinwu commented Jun 20, 2023

@qingxinwu qingxinwu added the spec Relates to the spec label Jun 20, 2023
spec.bs Show resolved Hide resolved
qingxinwu and others added 5 commits June 21, 2023 10:10
spec.bs Outdated
|reportResultOutputIDL|["{{ReportResultOutput/reportingBeaconMap}}"] in the
{{FencedFrameConfig}} as appropriate.
1. Return « |reportResultOutputIDL|["{{ReportResultOutput/signalsForWinner}}"], |browserSignals| ».
1. TODO: Store |reportUrl| and |reportingBeaconMap| in the {{FencedFrameConfig}} as appropriate.
Copy link
Collaborator

Choose a reason for hiding this comment

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

We're in parallel at this moment, right? Let's make this [=fenced frame config=] which is an infra struct, since I think we won't be constructing the platform object {{FencedFrameConfig}} here

Copy link
Collaborator Author

@qingxinwu qingxinwu Jun 22, 2023

Choose a reason for hiding this comment

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

yes, we're in parallel, since its caller [=generate and score bids=] is in parallel. So we cannot construct IDL objects when it's in parallel? I wanted to define and construct a browserSignals IDL object (already did that for generateBid's, and scoreAd's is under review) in methods like this that runs in parallel. If we cannot do that, we need to pass an ordered map to where we create a new |agent| and convert it to IDL object there? It adds more complexity.

Now I think I need to reconsider those in-parallels, for example, the top level caller. What I wanted to spec was that different component auctions can run in parallel without blocking each other, and script/signal fetches of different buyers can be run in parallel, etc., but it seems its scope is too wide in current spec.

Copy link
Collaborator

Choose a reason for hiding this comment

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

You can construct dictionaries in parallel. Not platform objects: https://webidl.spec.whatwg.org/#es-platform-objects

Copy link
Collaborator Author

@qingxinwu qingxinwu Jun 22, 2023

Choose a reason for hiding this comment

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

Done. Didn't notice it's an interface :)
Now it makes sense.

@JensenPaul JensenPaul merged commit 7cc77db into WICG:main Jun 22, 2023
github-actions bot added a commit that referenced this pull request Jun 22, 2023
SHA: 7cc77db
Reason: push, by JensenPaul

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@qingxinwu qingxinwu deleted the report branch June 22, 2023 21:05
github-actions bot added a commit to qingxinwu/turtledove that referenced this pull request Jun 22, 2023
SHA: 7cc77db
Reason: push, by qingxinwu

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit to morlovich/turtledove that referenced this pull request Jun 23, 2023
SHA: 7cc77db
Reason: push, by morlovich

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
spec Relates to the spec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants