-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8343467: Remove unnecessary @SuppressWarnings annotations (security) #21844
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
8343467: Remove unnecessary @SuppressWarnings annotations (security) #21844
Conversation
|
👋 Welcome back acobbs! A progress list of the required criteria for merging this PR into |
|
@archiecobbs This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 78 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
@archiecobbs The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
|
The files under |
@seanjmullan - thanks for the heads-up. Those files should be reverted in dc5340d. |
|
Thanks. Can you also explain why the unchecked and serial warning suppressions are no longer needed? |
Yes and no... The annoying answer would be: because they no longer suppress any warnings :) But I think what you're really asking is: how & why they were put there in the first place? And how over time did they somehow became no longer necessary? That's a great question, but I don't have any answers because these changes were generated from an automated analysis. |
Yes.
Can we find this out? It would be really useful to explain why the warnings are no longer an issue. |
I haven't checked exhaustively, but all of the ones I've checked appear to be due to either (a) the warning was never needed, or (b) a subsequent refinement of the warning itself which made the code no longer qualify as "warnable". For an example of (a) see commit 8fb70c7 which added For an example of (b), see commit b431c69 which added I guess the only other possibility is that the warning stopped working at some point due to a bug, but I haven't seen any examples of that. |
|
@archiecobbs this pull request can not be integrated into git checkout SuppressWarningsCleanup-security
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
@archiecobbs This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
/pingbot |
|
@archiecobbs Unknown command |
seanjmullan
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.
The bug needs an appropriate noreg label (I suggest noreg-cleanup). Otherwise, looks good to me.
Ah yes, thanks. I've added |
|
/integrate |
|
Going to push as commit 4b21fb9.
Your commit was automatically rebased without conflicts. |
|
@archiecobbs Pushed as commit 4b21fb9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this patch which removes unnecessary
@SuppressWarningsannotations.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21844/head:pull/21844$ git checkout pull/21844Update a local copy of the PR:
$ git checkout pull/21844$ git pull https://git.openjdk.org/jdk.git pull/21844/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21844View PR using the GUI difftool:
$ git pr show -t 21844Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21844.diff
Using Webrev
Link to Webrev Comment