Skip to content

Fix typo in packets-per-meaurement-period leaf - #1537

Open
hung1806vn wants to merge 1 commit into
openconfig:masterfrom
hung1806vn:patch-1
Open

Fix typo in packets-per-meaurement-period leaf#1537
hung1806vn wants to merge 1 commit into
openconfig:masterfrom
hung1806vn:patch-1

Conversation

@hung1806vn

Copy link
Copy Markdown

Fix typo in packets-per-meaurement-period leaf

@google-cla

google-cla Bot commented Aug 26, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request corrects a typo in the leaf name packets-per-meaurement-period to packets-per-measurement-period in the openconfig-oam-cfm.yang model. The reviewer suggested renaming the leaf to packets-per-measurement-interval instead, to maintain terminology consistency with the rest of the module which uses 'measurement interval' rather than 'measurement period'.

Comment on lines +1252 to 1255
leaf packets-per-measurement-period {
type uint16;
description "Number of probe packets to send within a measurement interval.";
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

There is a terminology inconsistency between the leaf name packets-per-measurement-period and the rest of the module. The module consistently uses the term "measurement interval" (e.g., the measurement-interval leaf on line 1206, and "measurement interval" in the description on line 1254).

To maintain consistency across the model, consider renaming this leaf to packets-per-measurement-interval.

Note: If you apply this change, please also update the reference in the description of packet-per-burst on line 1267. Additionally, since renaming a leaf is a backward-incompatible (breaking) change, the openconfig-version should be updated and a new revision entry should be added at the top of the file.

Suggested change
leaf packets-per-measurement-period {
type uint16;
description "Number of probe packets to send within a measurement interval.";
}
leaf packets-per-measurement-interval {
type uint16;
description "Number of probe packets to send within a measurement interval.";
}

@romeyod

romeyod commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

renaming the leaf is a backward incompatible change in this case. Not sure if worth deprecation and adding a new leaf

@dplore @navaneethyv

@earies

earies commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

renaming the leaf is a backward incompatible change in this case. Not sure if worth deprecation and adding a new leaf

@dplore @navaneethyv

agreed - one would also think it's caught by the first implementor vs. blindly implemented w/ a typo as well. No harm in introducing a new leaf, marking the existing as status deprecated just incase.


oc-ext:openconfig-version "0.1.0";

revision "2024-09-11" {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Add a new revision + increment version/reference per comments on compatibility


leaf packets-per-meaurement-period {
leaf packets-per-measurement-period {
type uint16;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Whether defining a new leaf or modifying existing, I'd probably suggest filling in any missing units statements that should otherwise be there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants