Redsandro

Can any of you get the debugger to work with Node 6.11? Even using `--inspect`, I can do breakpoints, but I cannot inspect any variables, as reported in issue https://github.com/kiddkai/atom-node-debugger/issues/237

I think it isn't that simple. Otherwise I'd be able to inspect values when changing the command line manually.

@willyelm said: > have you tried [atom-bugs-nodejs](https://atom.io/packages/atom-bugs-nodejs)? it does support sourcemaps I'm getting `404`.

@alexandernst said: > Sometimes some variables are missing, sometimes variables get duplicated. I can confirm this. I sometimes see double variables or occasionally a value from the previous/next variable. I...

It's difficult. I encounter this now and again with big code. When I try to simplify this, into reproduction code, it starts working. :( The problem with the hidden vars...

I have the same problem. When inspecting the "background page" console, it appears that there are CORS issues. More specifically, `XMLHttpRequest` is blocked due to deluge json api not returning...

I just might take you up on that @glego. You might want to split up the remaining two requests because issues are [automatically closed](https://help.github.com/articles/closing-issues-using-keywords/) by merged commits, and we can't...

I didn't mean to suggest literally adding emoji's, it was just the quickest way of illustrating what I meant with a _"polite way of indicating"._ :sweat_smile: What I'm looking for...

Bars without colors sounds good too. So for people who don't care, it's easy on the eyes. For people who do care, they can look up what the bars mean....

Linux Mint 21 (released last week) joins the conversation... Unrelated to OneDrive though. This issue occurs with _any_ Duplicati job.