I recently installed SonarLint in IDEA 2016.2 and it has been very helpful, but one minor annoyance is the banner for a minor issue won't go away. I realize that this is an issue that needs to be addressed, but I can't control the Sonar project settings and updating all these files would involve doing a huge commit. I know how to disable the syntax highlighting for minor errors, but how to disable the banner?
Currently, that's not possible.
The plan is to track issues when connected to a SonarQube server and hide issues that are marked as resolved: https://jira.sonarsource.com/browse/SLI-83
In your case, you wil be able to mark all minor issues in those files as "won't fix".
Related
TL;DR -> Force code smells to apear as SonarCloud issues on IDE
I got SonarLint plugin (vscode) installed locally and configured with external SonarCloud rules (by my organization's project).
The thing is even though it is well configured, some issues fail to count as an acttual issue locally on my IDE and only apears online (e.g. github integration).
I have not yet realized what is common between those slippery sonarcloud issues, might be code smells.
I have seen some StackOverflow questions regarding that matter, but have not yet encountered an answer which explicitly suggests a workaround or a method to configure it as I wish.
Did anyone ever manage to work it out?
I'm working on multiple projects at the same time which are inter dependent. Sometimes, when one developer pushes updates to one project (for example Liquibase changes), they are picked up by my IntelliJ which immediately complains about missing columns when I restart the project. I did not explicitly issue any fetch/pull or update request against the remote repository. This is kind of annoying because I am then forced to pull all the new changes locally.
I remember my old IntelliJ version behaving normally (2019) so this is a new "feature" I guess? How can I disable it?
Could you please share screenshots of an issue? IDE doesn't run pull/fetch or upgrade automatically if you are using Git, but there is a chance that you may have Git Toolbox plugin installed and it has a feature for Auto-fetch and you need to disable it in settings
Question is what steps can I take to debug this?
It does very occasionally auto-save itself, but not on change of active window as previously. I can't yet reproduce a specific cause of this (very occasional) autosave.
I have all auto-save options as per default:
I recently did brew upgrade including fswatch. Would I be right in assuming IntelliJ would use its own though, not brew's fswatch if installed?
Another possibility is it's a Mac OS Privacy thing; a Catalina update seems to have broken one program which expected disk access to be available, now it's not; not sure if Intellij has lost some kind of OS permission to do (auto) saves(?), while this doesn't affect a user issued command to save, which works fine.
I use IntelliJ IDEA community (currently 2017.2) from both Windows and Linux with settings shared between the two via the settings repository. In the main this works well but sometimes I will open IntelliJ from either OS and find the font sizes for the editor, console and UI have increased from 14 to 17.
I notice that when this happens it's because FONT_SCALE in ~/.IdeaIC2017.2/config/settingsRepository/repository/ui.lnf.xml has been changed from 1.0 to 1.25 by the commit made when I previously closed IntelliJ on the other OS. This seems to happen occasionally in both directions. I'm not changing anything myself that should affect this.
How do I prevent this from happening?
I've reported a bug, please follow for updates:
IDEA-172611 Don't share FONT_SCALE setting between different operating systems
I feel like I'm experiencing a common problem, but I wasn't able to find anyone asking about it.
As the title indicates, we're forced to use AccuRev for SCM. We have our development stream under our QA stream. Let's say we're working on a big project that will be in QA for weeks before being released (we're following a scrum strategy). In the meantime, there's a bug fix that needs to go out before this big project. The problem is the bug fix affects some of the same files the big project uses. How would I get my files from development to production, without bringing the big project with me?
Sorry, I hope that makes sense!
Thanks!
If you are using the change package feature in AccuRev, you can select that issue and just promote those changes into the production stream.
Otherwise, you will need to determine the promote transaction(s) of the of the bug you fixed in development and change palette those fixes into production.
I think I found a solution that will work for us.
I plan on creating a snapshot off of the development stream after each successful deployment to production. Bug fixes/smaller projects will work off of this snapshot. That way I can keep anything I'm currently working on in DEV from getting inherited into my bug fix. When I'm ready to deploy my bug fix, I'll create another snapshot and re-parent my big project there. Then I'll revert the change package in QA and development, re-parent my bug fix to development, and promote as normal.
It's a slightly modified version of what's explained in this article: https://accurev.wordpress.com/2008/03/27/pattern-for-stable-development/