Revert "Merge pull request #170 from gtannous-spec/nodeptpdevice-feat"#175
Conversation
Summary of ChangesHello @gtannous-spec, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request performs a complete revert of a previous merge, effectively undoing changes related to the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request reverts a previous feature that added more detailed hardware information to the NodePtpDevice status. The changes consistently remove the new fields from the HardwareInfo struct in api/v1/nodeptpdevice_types.go and update the corresponding Custom Resource Definitions in the various YAML manifest files. The revert appears to be complete and correct, with no lingering artifacts from the reverted feature in the changed files.
This reverts commit f53b758, reversing changes made to 2bf6cc1.
This changes were reverted because it was causing vendor issues in the linuxptp-daemon PR#152
Once fixed there, I will push a new PR to update the api again.