-
Notifications
You must be signed in to change notification settings - Fork 72
fix(tc): parse error message to correct kind #229
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
fix(tc): parse error message to correct kind #229
Conversation
Summary of ChangesHello @ver-nyan, 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 focuses on improving the clarity and accuracy of error messages within the Traffic Control (TC) filter parsing logic. Specifically, it rectifies misleading error contexts for 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.
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 error messages in the parsing logic for u32 and matchall TC filters. Specifically, when parsing TCA_U32_CLASSID and TCA_MATCHALL_CLASSID, the error context incorrectly referred to ..._UNSPEC constants. The changes fix these error messages to correctly reference the ..._CLASSID constants, which will improve clarity when debugging parsing failures. The fixes are accurate, targeted, and improve the code's maintainability. I have no further suggestions.
e5fa7ba to
b3397b9
Compare
*_UNSPEC -> *_CLASSID in "u32" & "matchall" TC filters|
/gemini review |
There was a problem hiding this comment.
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 refines error messages across several TC filter and qdisc parsing functions. The changes update generic or incorrect error messages to be more specific to the context of the parsing failure (e.g., TCA_U32_UNSPEC to TCA_U32_CLASSID, u32 nla to matchall nla or fq_codel nla). These improvements enhance the debuggability and clarity of error reporting within the tc module. All comments are positive and highlight these beneficial changes.
Fixes parse error message in the TC filters: - "u32" & "matchall" for `*_CLASSID`. - "matchall" & "fq_codel" for `DefaultNla`
b3397b9 to
42a5c02
Compare
Fixes the
parse()error message for TC filters:"u32"&"matchall"for*_CLASSID"matchall"&"fq_codel"forDefaultNla