fix(sec): upgrade networkx to #8613
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
skrdgraph
approved these changes
Jan 18, 2023
There was a problem hiding this comment.
Thanks for the submission @whiteChen233 .. this looks okay.
Please note this portion of the code is not actively supported today. And when we decide to support it, this will be helpful. Hence we are okay to get this in.
Can you please sign the CLA agreement? (we cannot merge this otherwise)
|
@whiteChen233 could you please sign the CLA for us to be able to accept this PR? We are in the process of cleaning up old PRs & getting them merged - your help will be appreciated. |
mangalaman93
approved these changes
Feb 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What happened？
There are 1 security vulnerabilities found in networkx 2.4
What did I do？
Upgrade networkx from 2.4 to for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
The specification of the pull request
PR Specification from OSCS