Skip to content

Require EPP validation for complex OT&E stats#3107

Merged
gbrodman merged 1 commit into
google:masterfrom
gbrodman:oteStats
Jul 7, 2026
Merged

Require EPP validation for complex OT&E stats#3107
gbrodman merged 1 commit into
google:masterfrom
gbrodman:oteStats

Conversation

@gbrodman

@gbrodman gbrodman commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Previously, if there were no XML bytes somehow, it'd increment a bunch of counts for requirements that shouldn't be incremented. We should only increment these values if we have the data to do so.

Note: this doesn't happen and shouldn't happen, so there's no issues
currently occurring, but this code is more correct anyway.


This change is Reviewable

@gbrodman gbrodman requested a review from CydeWeys July 1, 2026 17:39

@CydeWeys CydeWeys left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't understand what problem this is solving or how this situation could come to be.

@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@gbrodman gbrodman left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

When registering OT&E stats we inspect history entries for a registrar. Many of the OT&E checks require inspecting the EPP xml bytes to figure out if the check was hit, e.g. DOMAIN_CREATES_START_DATE_SUNRISE.

There should always be XML bytes but if they were missing for some reason, previously this would return true for every single type of check that inspects XML bytes if the XML bytes were absent.

@gbrodman made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@CydeWeys CydeWeys left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

But why would they be missing? Under what circumstances does that happen? Are you writing this PR because this is an issue we faced? (And if so, what caused it?)

@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@CydeWeys CydeWeys left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I agree that the new code is safer, and I'm not opposed in principle, I just feel like I'm still missing information?

@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@gbrodman gbrodman left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

They shouldn't be. As far as I'm aware they haven't been. But this is incorrect behavior nonetheless. This was one of the issues flagged, in section B2.

@gbrodman made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@CydeWeys CydeWeys left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Cool. Can you just update the commit description to make it clear that isn't responding to any known data/issue in our system, but that the new code is more correct nonetheless.

@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

@CydeWeys CydeWeys left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

:lgtm:

@CydeWeys made 1 comment.
Reviewable status: 0 of 2 files reviewed, all discussions resolved.

Previously, if there were no XML bytes somehow, it'd increment a bunch
of counts for requirements that shouldn't be incremented. We should only
increment these values if we have the data to do so.

Note: this doesn't happen and shouldn't happen, so there's no issues
currently occurring, but this code is more correct anyway.
@gbrodman gbrodman enabled auto-merge July 7, 2026 19:01
@gbrodman gbrodman added this pull request to the merge queue Jul 7, 2026
Merged via the queue into google:master with commit 0bf0b4f Jul 7, 2026
15 of 16 checks passed
@gbrodman gbrodman deleted the oteStats branch July 7, 2026 22:32
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.

2 participants