Google Dev-Tools don't show Error - google-chrome-devtools

please have a look at this screenshot:
Something is not working correctly on my site and I therefore want to debug it. Dev-tools shows that I have 5 Errors and 1 Warning, but when I CLICK on them, nothing happens. It doesn't bring me to a view, where the errors are shown.
I then search in the network panel, where the errors are shown (although I have to scroll through all requests).
The question is, shouldn't I get redirected to where the errors are shown in a list? (At least this is how it worked in the past for me.)

It might happens that console view with the errors was resized and the only caption of the console pane are visible. Another option is the filters mentioned in the comments.
If the errors and warnings were filtered out then you will see the console but it will have only marker that some messages were filtered out.

Related

What is the moving line at the top of vscode, and how can I get rid of it?

Recently VSCode is showing an animated line, that moves constantly from the left to the right. The movement is distracting when I am trying to code.
What is the line, and how can I disable it?
This is because it's "loading" something in the background.
Display the Ouptut console shiftcmd/ctrlu (or: View > Output) and on the right, in a selectable list, check the different tasks or logs to see what process is still pending.
Sometimes it's a plugin which is stuck, or a wrong configuration of your project.
It could also simply be a bug in VSCode.

How to view original location using source maps in Chrome?

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.

How do I make TODOs not show up as errors in eclim?

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...

Why do some websites take longer to load when clicking "view source"?

I'm trying to figure out how the sublime text community package list works over at http://wbond.net/sublime_packages/community
The page itself displays after about a second and seems fine to use. You can inspect element too, and that also works fine, the dev tools window opens up straight away.
But if you click "view source", it takes absolutely ages for the source code to display. I've tried this on lots of different browsers. Why is this?
The slowness is caused by the syntax highlighter. Chrome's view-source: attempts to highlight the whole file at once, which takes some time on a 1.5MB file.
Press Shift + Esc to show Chrome's Task Manager, and you will see that the CPU shoots up on "view source". If you wait a little longer, the "Page(s) Unresponsive" dialog will show up (as shown below).
This bug has been reported before at https://code.google.com/p/chromium/issues/detail?id=128293
The page is extremely large. It has a total size of 1,5MB so the source viewers have some troubles loading that.
There are about 35000 lines of source code in there, a pretty hefty HTML file I would say :)

Xcode 4 equivalent of the debugger

In the older version of Xcode, I used to press cmd-shift-Y to get a window (I think it was the debugger) to see where errors were coming from in my iPhone app.
But now, I always see question marks, and can't ever seem to properly track where the error is coming from. How do I do it in the new Xcode?
The screenshot you have posted is thread view of debugger actually. When you get an error you can still hit Cmd+Shift+Y which is a keyboard shortcut to hide/show the debug area. It will pop up in main editor area from bottom.
In the debug area, the top horizontal bar shows the buttons to continue, Step Into, Step Over etc. In this horizontal bar, the last item on right hand side is the function name which was executed the last. You can click on that to see the stack trace and track from what function the error is coming. The function which was executed recently in the trace would be the first item in the list and the main function would be the last in this list.
Hope this helps.