I've one problem on Intellij IDEA.. There are everything working but, IDEA shows warnings like this.
Here are some screenshots:
And when I compile it, it's working:
Please, who can tell me, where is a problem?
I watched Duplicates questions and can't find answer for it!
I Fix this problem: just two steps
File --> Invalidate Chaches / restart
There is one warning: you clear your local history..
Idea say you:
The caches will be invalidated and rebuilt on the next startup.
WARNING: Local History will be also cleared.
Would you like to continue?
Accept it and wait, after restarting, problem has been fixed.
Related
I'm using Intellij IDEA 2017.1.5 with the Golang Plugin.
When I run Analyze > Inspect Code > Whole Project, the Inspection Results always include "Unused Exported Function" warnings, even though my project codes clearly use those functions. The same goes for some Global Variables and Constants.
When I comment-out those "unused" functions and variables, I encounter "Undefined Function" and "Undefined Variable" errors, and when I put them back, the errors disappear, so I know they are actually being used within my project.
Is there a way to make these wrong warnings go away, or "refresh" the compiler's Code Analysis? And is this a known issue with Intellij IDEA or the Golang Plugin in general, and has anybody else encountered this?
It's really annoying because I'm aiming for 0 Warnings and these ones never go away.
Upgrade to IDEA Ultimate 2017.3+ or use GoLand and see if the error still happens.
The plugin for 2017.1 is really old and a lot of changes have happened since then.
If the issue still happens, then report it to https://youtrack.jetbrains.com/issues/Go and make sure to include a way to reproduce issue.
Intellij idea wraps console output in the run window, how I can increase N after which wrap happens?
as you can see wrap happened on the last line, how I can configure IDE not to wrap so short lines? I have a lot of free space in this window
P.S. windows, golang plugin for Intellij idea
Thanks!
there's already a ticket for this on the issue tracker of the plugin, please see this issue. However, it's dependent on a platform issue, please see this issue. My advice would be to track either of the issue in order to know when this is fixed, unfortunately it's not much that the plugin can do right now as far as I can tell.
Since I started using CocoaPods, I've been having weird location related messages all the time, and some arch-related ones too.
I've been trying the whole day to figure out why it was happening, until I create a new Xcode project from scratch and realize the issue wasn't project-related all along.
Here's what's happening:
I always get those everywhere as well:
Not sure if related but I get those often too:
Anybody has those as well? What should I do?
Thanks!
I had to switch Build Active Architectures Only for debug to Yes and it let the build run.
I have a rather large solution of about 20 projects, that I have worked with for about three years now. In recent weeks, I seemed to have lost the ability to just press "Run and Debug" on my toolbar. If I do this, I lose all ability to debug and use breakpoints. My breakpoints all get a little yellow exclamation point on them and never run. Below is an example.
To fix this so I can get debugging again I have to fully clean the project. If I try to run after cleaning, i get an error saying the file does not exist. So I have to then fully re-build the project before I can run. It works just once, and then I lose my ability to debug again. Below is the error if I don't manually build first:
This seems to be effecting several (maybe all) projects in my solution and is causing extremely large problems for me. Some of my projects I need to breakpoints to verify data before it runs, and if I forget to do this, it runs before verifying.
Any help in fixing this would be amazing. Under solution settings, my start up project i set to "Current Selection" if that helps.
UPDATE:
So far under solution settings -> configuration a bunch of my items had "Build" not selected for Debug. Not sure how that happened, but updating that for now seems to have solved it. If it goes to not building each time again I will re-update, but for now I think that solved the issue.
I've got serious issues with XCode right now and i cant really figure out what to do, or even whats wrong.
The project i'm working on was working perfectly yesterday, but today when i started it i got like 20 "Redefinition of enumerator" errors, and to the point where "Too many errors emitted. Stopping now".
The wierd part is that ALL my backups of the project does this aswell. Even the ones from 2,3 or 4 days ago which hasnt been altered.
No other project seems to be affected by this.
I've tried Cleaning the build, removing Derived data, checking for duplicate files somehow (even though that shouldnt be possible), all linker seems to be in order. Anyone got any tips for me?
Thank you!
you should import
#import "Facebook.h"
instead
#import <FacebookSDK/FacebookSDK.h>
I just had this exact problem about "Redefinition of enumerator" errors coming out of nowhere.
The problem was that accidentally (maybe some unintended drag with the mouse) I had copied one of the project directories into some other, thus duplicating it.
On the other hand I use git and generally was using 'git status -uno' which hides untracked files.
So I was not seeing the untracked duplicated directory that was duplicating enums in the project, from my perspective I had a clean HEAD with weird errors :S
Lesson learned: use .gitignore rather than '-uno' option
This issue still happens in 2019 smh.
If you get this go check File->Workspace Settings and set build system to Legacy Build System. This should fix the issue.
I had the same error and was really stuck. But found that the project folder nam had white spaces. I changed that and the error went off!
Eg: Changed folder name My Project to MyProject
For anyone has the same problem, who pulled out hair for hours/days.
Let's double check and remove redundant Header Search Paths, delete Derived Data if needed.
After that, the issue will be resolved.