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 new template for Fsas Si-R show ether #1971

Merged
merged 8 commits into from
Jan 14, 2025

Conversation

caribouHY
Copy link
Contributor

I added a new template for Fsas Si-R show ether.

Comment on lines 13 to 17
status: "100M Full MDI"
status_auto: ""
status_duplex: "Full"
status_mdi: "MDI"
status_speed: "100M"
Copy link
Contributor

Choose a reason for hiding this comment

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

It's a bit of a bummer the status data is captured twice.
I do notice that's likely because of the offline (backup) and disable statuses.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you for the review. Would you prefer not to capture STATUS when not offline or disalble?

Suggested change
status: "100M Full MDI"
status_auto: ""
status_duplex: "Full"
status_mdi: "MDI"
status_speed: "100M"
status: ""
status_auto: ""
status_duplex: "Full"
status_mdi: "MDI"
status_speed: "100M"
  ^status\s+:\s+(${STATUS_AUTO}\s+)?${STATUS_SPEED}\s+${STATUS_DUPLEX}\s+${STATUS_MDI}\s*$$

Copy link
Contributor

@mjbear mjbear Jan 12, 2025

Choose a reason for hiding this comment

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

Thank you for the review. Would you prefer not to capture STATUS when not offline or disalble?

  ^status\s+:\s+(${STATUS_AUTO}\s+)?${STATUS_SPEED}\s+${STATUS_DUPLEX}\s+${STATUS_MDI}\s*$$

@jmcgill298 @jvanderaa @itdependsnetworks
What are your thoughts on the STATUS sometimes capturing data that is captured in other capture groups?

The downside here is that the STATUS capture group would have to become much more rigid (to be the two statuses in the present test data) so it doesn't match the speed/duplex/MDI.

Update: Change sentence grammar.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think if the goal is to split the status field into multiple capture groups, then the status field should capture auto, disable, and offline text, and then it would be an empty string if it is set to a particular speed.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think if the goal is to split the status field into multiple capture groups, then the status field should capture auto, disable, and offline text, and then it would be an empty string if it is set to a particular speed.

I like this idea.
I cooked up some suggestions.

Comment on lines 4 to 5
Value STATUS (.+?)
Value STATUS_AUTO (auto)
Copy link
Contributor

@mjbear mjbear Jan 14, 2025

Choose a reason for hiding this comment

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

Support one and two word statuses (ex: offline (backup)).

Suggested change
Value STATUS (.+?)
Value STATUS_AUTO (auto)
Value STATUS (\S+(\s+\S+)?)

Copy link
Contributor

Choose a reason for hiding this comment

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

The "commit suggestion" button can help easily merge in suggestions. Thank you.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

STATUS have to support the following status:

  • offline
  • offline (backup)
  • offline (startup down)
  • offline (recovery manual)

I added a test case.

@jmcgill298 jmcgill298 merged commit 380f1be into networktocode:master Jan 14, 2025
10 checks passed
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