这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@apasel422
Copy link
Collaborator

@apasel422 apasel422 commented Sep 25, 2025

IMO the benefit of the previous non-normative guidance around how the earliest epoch index might be chosen was unclear, and made it hard to understand what was going on in the simulator with respect to expiry vs lookback. In particular, there was no indication of why implementations might want to vary this value by site, and the non-normative guidance didn't even suggest doing so.

Instead, we normatively define the earliest epoch index in terms of the maximum lookback to permit the full range of impressions to be queried using a maximal lookbackDays value.


Preview | Diff

@apasel422 apasel422 changed the title Add e2e test for impression expiry Normatively define earliest epoch index in terms of maximum lookback Sep 25, 2025
@apasel422 apasel422 marked this pull request as ready for review September 25, 2025 14:46
@csharrison
Copy link
Collaborator

This seems fine to me. I don't see any real reason why these should use different constants.

Copy link
Member

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

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

Much better, thanks.

@martinthomson martinthomson merged commit 35bda38 into w3c:main Sep 26, 2025
3 checks passed
@apasel422 apasel422 deleted the expiry branch September 26, 2025 01:24
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