-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[201911] DellEMC platform API 2.0 for Z9264f, S5232f #5637
Conversation
This pull request introduces 36 alerts when merging a173745 into 44abb50 - view on LGTM.com new alerts:
|
This pull request introduces 26 alerts when merging 459f49f into 44abb50 - view on LGTM.com new alerts:
|
This pull request introduces 15 alerts when merging 53bbc02 into 44abb50 - view on LGTM.com new alerts:
|
This pull request introduces 14 alerts when merging d55dc7c into 44abb50 - view on LGTM.com new alerts:
|
can you fix the ltgm alerts? |
Hi @lguohan , 10 for Wrong number of arguments in a class instantiation.
|
Yes, this seems to be a bug/limitation of LGTM. With the platform API, we have multiple definitions of each class, provided by each vendor. LGTM generates "Wrong number of arguments in a class instantiation" alerts because when it attempts to find the class definition, it finds a different vendor's implementation, and if they modified the definition, it thinks there is a problem and generates a false alarm. There's not much we can do about this unless LGTM makes their algorithm smarter. |
This pull request introduces 16 alerts when merging 40f1ba7 into 36ea042 - view on LGTM.com new alerts:
|
This pull request introduces 16 alerts when merging 87f73a9 into 36ea042 - view on LGTM.com new alerts:
|
retest broadcom please |
1 similar comment
retest broadcom please |
retest broadcom please |
1 similar comment
retest broadcom please |
This pull request introduces 16 alerts when merging 2cfd812 into ea28f2d - view on LGTM.com new alerts:
|
retest mellanox please |
retest broadcom please |
retest mellanox please |
- Why I did it
Added API 2.0 in 201911 branch
- How to verify it
Executed necessary API's through python shell
s5232_API_2.0_UT.txt
z9264f_API_2.0_UT.txt