-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18687. Remove json-smart dependency #5549
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
Conversation
|
💔 -1 overall
This message was automatically generated. |
e69ac0b to
fc03294
Compare
|
💔 -1 overall
This message was automatically generated. |
ayushtkn
left a comment
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.
LGTM
|
@ayushtkn I'm not sure yet about this change. Those test failures appear to be consistent issues. |
|
@pjfanning no worries, I am sure about them, they aren't related. They are failing in the daily build as well. Need to chase them, not getting time unfortunately The daily build test result. I think all are same as in this PR |
|
Thanks @ayushtkn for clarifying. I ran the MR tests locally but they just timed out and I wasn't really sure how to proceed. |
|
Do you also plan to upgrade nimbus-jose-jwt to a newer version since the current version shades json-smart 1.3.2 which gets flagged by scanners for both CVE-2021-31684 and CVE-2023-1370? nimbus-jose-jwt also dropped the json-smart dependency completely with nimbus-jose-jwt 9.24 and replaces it with Gson 2.9.1 (shaded) as seen in the commit history here: https://bitbucket.org/connect2id/nimbus-jose-jwt/commits/tag/9.24 So upgrading nimbus-jose-jwt from 9.8.1 to >9.24.4 could help completely get rid of json-smart from scanners and address HADOOP-18687. Related discussion here: #3299 |
|
Could you raise a separate Jira for nimbus? |
|
I don't have an account there and not sure how easy it is to get one |
|
Merged Thanx @pjfanning for the contribution. @degant feel free to create a new ticket for nimbus. You can request to create a jira account by filling this form |
|
Thanks for filing it! I went ahead and requested an account on jira |
|
For some strange reason, seems the builds have failing on compilation post this Might not be related, but since it is failing post this only, have reverted this. Would require a rebased PR again or if I find there is something else, can commit it again directly |
…ted by PJ Fanning." This reverts commit b6c0ec7.
|
I have triggered those builds again post reverting this. @pjfanning can you check once. I think it may be this commit is conflicting with |
|
Context-> #5575 (comment) Raised an Infra ticket as well: INFRA-24480 |
|
@ayushtkn can we try again tomorrow perhaps? I have a couple of other PRs that are rebuilding that were affected by a similar issue to this when they first ran. |
|
Sure, I will commit it tomorrow, Infra confirmed that the issue was on their part only. Sorry, for creating unnecessary noise. |
|
…J Fanning. Signed-off-by: Ayush Saxena <[email protected]>
|
I have pushed again 🤞 |
…d by PJ Fanning. Signed-off-by: Ayush Saxena <[email protected]>
Contains * HADOOP-18687. hadoop-auth: remove unnecessary dependency on json-smart (#5524) Contributed by Michiel de Jong * HADOOP-18687. Remove json-smart dependency. (#5549). Contributed by PJ Fanning.
…d by PJ Fanning. Signed-off-by: Ayush Saxena <[email protected]>
…ntributed by PJ Fanning." This reverts commit b6c0ec7.
complete removal of json-smart jar