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

two platforms supporting S3IP SYSFS (TCS8400, TCS9400) #12386

Merged
merged 5 commits into from
Dec 18, 2022

Conversation

tianshangfei
Copy link
Contributor

@tianshangfei tianshangfei commented Oct 13, 2022

Why I did it

Add two platform that support s3IP framework

How I did it

Add two platforms supporting S3IP SYSFS (TCS8400, TCS9400)

How to verify it

Manual test

Which release branch to backport (provide reason below if selected)

A demo driver base on s3ip framework will display the sysfs node which conforms to the s3ip sysfs specification

  • 202211

Description for the changelog

two platforms supporting S3IP SYSFS (TCS8400, TCS9400)

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@lgtm-com
Copy link

lgtm-com bot commented Oct 13, 2022

This pull request introduces 54 alerts when merging e96961d into 7087763 - view on LGTM.com

new alerts:

  • 39 for Wrong number of arguments in a class instantiation
  • 14 for 'import *' may pollute namespace
  • 1 for Wrong name for an argument in a class instantiation

@@ -0,0 +1,63 @@
<DeviceMiniGraph xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="Microsoft.Search.Autopilot.Evolution">
Copy link
Collaborator

Choose a reason for hiding this comment

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

please remove minigraph, no longer used.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok,I'll update the code

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The code has been updated

Signed-off-by: tianshangfei <tian_shangfei@163.com>
@lgtm-com
Copy link

lgtm-com bot commented Oct 21, 2022

This pull request introduces 41 alerts when merging 85c5344 into 3587489 - view on LGTM.com

new alerts:

  • 39 for Wrong number of arguments in a class instantiation
  • 1 for 'import *' may pollute namespace
  • 1 for Wrong name for an argument in a class instantiation

@adyeung
Copy link
Collaborator

adyeung commented Nov 22, 2022

@FuzailBrcm pls help review

Signed-off-by: tianshangfei <tian_shangfei@163.com>
@lgtm-com
Copy link

lgtm-com bot commented Dec 4, 2022

This pull request introduces 42 alerts when merging cfbb047 into 5281f6c - view on LGTM.com

new alerts:

  • 40 for Wrong number of arguments in a class instantiation
  • 1 for 'import *' may pollute namespace
  • 1 for Wrong name for an argument in a class instantiation

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.

@prgeor
Copy link
Contributor

prgeor commented Dec 5, 2022

@tianshangfei could you fix LGTM alert?

@tianshangfei
Copy link
Contributor Author

@tianshangfei could you fix LGTM alert?

It's been cleaned up once. Some of them are false positives. I'll go over them again

@tianshangfei
Copy link
Contributor Author

@tianshangfei could you fix LGTM alert?

I have checked again, LGTM Alerts are divided into two situations

  1. LGTM false positive
  2. Not this pull request code
    These Alerts can't be fixed, The summary is shown in the table.
    image

See attachment for details.

lgtm_check.docx

@tianshangfei
Copy link
Contributor Author

@prgeor

@@ -0,0 +1,168 @@
#!/usr/bin/env python3
# -*- coding: UTF-8 -*-
Copy link
Contributor

@prgeor prgeor Dec 8, 2022

Choose a reason for hiding this comment

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

not sure why we need to declare since UTF-8 is the default source encoding:-https://peps.python.org/pep-3120/ for Python3

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is redundant code and has been removed,thandks

Signed-off-by: tianshangfei <tian_shangfei@163.com>
@StormLiangMS
Copy link
Contributor

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@StormLiangMS
Copy link
Contributor

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@StormLiangMS StormLiangMS left a comment

Choose a reason for hiding this comment

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

LGTM

@StormLiangMS StormLiangMS merged commit b65e06f into sonic-net:master Dec 18, 2022
mssonicbld pushed a commit to mssonicbld/sonic-buildimage that referenced this pull request Jan 1, 2023
Why I did it
Add two platform that support s3IP framework

How I did it
Add two platforms supporting S3IP SYSFS (TCS8400, TCS9400)

How to verify it
Manual test
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202211: #13210

StormLiangMS pushed a commit that referenced this pull request Jan 9, 2023
Why I did it
Add two platform that support s3IP framework

How I did it
Add two platforms supporting S3IP SYSFS (TCS8400, TCS9400)

How to verify it
Manual test

Co-authored-by: tianshangfei <31125751+tianshangfei@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants