Using Netbeans 8.0.2, I'm getting an error (red circle/exclamation mark) on the tab for the html file, but there is no error shown in the html itself:
While just an irritant, it does keep drawing my eye to it. I'd like to make it either go away or show exactly where the error is, but I can't find anything online about this particular problem.
Two more things to try:
check Action Items window to see if there is something (Window->Action Items)
could be issue of NetBeans - check IDE log if there is some exception via View->IDE log
I usually just add a space in the file and then save it. It is annoying but it does the job.
Related
I am new to Flutter. So sorry if my question is silly...
In Flutter is there a way to see which line throws an error?
E.g. I have this in console.
And this in the stimulator.
Can I understand from it which line throws it?
You can see the line of code that has error in your screenshot bro, all you need to do is read it and we can see that the error is in #1.
it says that you story.dart has error on line 200
Using the console
See all the files in blue on the console? They represent all files (yours and those from the Flutter SDK and libraries) connected to the error message.
There is a high chance that the line that throws an/the error is not from the libraries but from your own code. So, what do you have to do?
Scan all files in blue that are from your own code and look for the one that has the strongest relationship with the error message.
For example, in your case, story.dart is your own code. Ctrl + click on story.dart files in blue to see the line that may have caused the error/exception. In your case, there is a high chance that you are trying to read or delete an element from an empty list.
You can also use the VSCode debugger to do this
I have had the same problem: VSCode opening flutter source files and pointing to an exception in them, instead of in mi code. After reading #user2740650 comment, a looked carefully to the bottom bar, and discovered the Debug my code + packages + SDK text in it.
Screen capture of bottom bar in VSCode
I clicked on it and switched to Debug my code, and my problem was solved!
Source maps enabled in Chrome.
I'm able to browse through the original files.
However I can't figure out how to go from the stack trace to the place of the error in the original files.
I am getting an error in my all.min.js file, containing all of my JS minified.
I click the link in the stack trace and it takes me to this:
How can I get to the location in the original file from here?
It looks like this feature hasn't been implemented or isn't possible.
Something that helps is clicking the 'un-minify' ('fix indent') button in the bottom left corner of the code window.
That shows me where the error is happening in a more readable way, although it's simply an indentation fix.
I've seem to have lost the ability in my Eclipse to auto-correct errors in my source code lines.
For example, a line like this:
Date date = new Date();
has red jagged lines beneath the Date() part. Previously I could mouse hover over it see a popup menu of options to fix it. Now I all I ever get is a popup with the text "Cannot resolve to a type".
The only change I can think of that I've made and I don't know if it has anything to do with this problem, is that I started editing my .java files with an outside editor. Then focusing back into Eclipse I get a popup saying the source has changed and do I want to update so I say OK.
Sometimes I will edit inside Eclipse and sometimes i will edit the source outside of Eclipse. I'm not sure if this is a bad practice or not?
Its your wish to edit Java files outside or inside eclipse. But Java editor has many features which are very helpful to developers. I suggest to edit Java files inside eclipse only.If you find other editors are good or you used to it then no problem you can edit Java files out side eclipse also. The problem you mentioned in not related to it. But make sure that changes are applied before building project in eclipse.
Solution
This occurs whenever there are multiple classes are available with the same name in you build path then eclipse don't know which one to import by default. So keep the caret on the error line and press Ctrl+1. Then a eclipse gives options to user to import one among these. See the picture below. Choose the right one then error will disappear.
I just started using eclim (combined with YouCompleteMe), and it's great. There is one thing that's bothering me, though, and I can't figure out how to fix it. The syntax checker runs on file saves, which is good, but it shows TODOs in the file as errors. So, in the error column on the left side of the window, an error appears when there's a TODO in the file. I've searched through all of eclim's vim files, tried a couple of eclim settings (g:EclimTodoSearchPattern and g:EclimTodoSearchExtensions), and none of those fixed the problem. Indeed, it seems like eclim's :ProjectTodo and :Todo commands aren't what's causing this, because they produce a different kind of error and location list (different colors).
I'm thinking that eclim gets a list of issues from eclipse, including eclipse's task tags (which in turn are automatically generated from any TODO text), and that's what it shows. So I tried to find a way to get eclipse not to show the task tag, but that was also unsuccessful. I can get task tags to not show up in the "Tasks" view in eclipse, but I can't get them to be removed from the file itself. Any idea of what I can do here? I would really like to be able to see a real syntax error with eclim, fix it, and see the left error bar go away, so that I know I don't have any more compilation errors. I don't want a TODO to pretend that it's a compilation error.
Well, I found one way to solve this problem, though it's not totally ideal. Eclim has a "sign level" that determines what severity of message it gets from eclipse to show in the vim window. It turns out that eclipse's task tags show up as severity level "warning", so if you set the sign level to something above "warning", the task tags no longer show up. This is done with the following line in a .vimrc:
let g:EclimSignLevel = 2
It would be better if I could lower the severity on the eclipse side, so I could still see other "warning" messages. There's probably a setting for that somewhere...
I need to disable the "Exceptions" window that pops when you encounter an IDE error in Netbeans - I always report when I can but is driving me crazy right now.
Don't get me wrong, I love the application, but I'm getting tired of the errors on my screen, sometimes needing to delete a file and create him again to enable me to continue.
I can drag it to the side but my mouse loses focus.
I'm using Windows 7 and latest version of Java (netbeans PHP ide)
Is this possible?
You need to modify <netbeans-install-dir>/etc/netbeans.conf
Add
-J-Dnetbeans.exception.alert.min.level=99999 -J-Dnetbeans.exception.report.min.level=99999
to the netbeans_default_options entry.
You have to set some properties when launching Netbeans. Modify your application configuration in "nbproject/platform.properties" by finding a line run.args.extra=... and adding at the end:
-J-Dnetbeans.exception.alert.min.level=99999 -J-Dnetbeans.exception.report.min.level=99999
You'll find the details in Netbeans' wiki.
I would recommend using -J-Dnetbeans.exception.report.min.level=99999 but not the other one. This means the error icon will still appear when there is a problem, and you can report the error if you have a moment, but no dialog will pop up without your asking it to.