Can't create a view for Notification instance. Please register a view provider. about package-deps

[steelbrain]

That is super-super weird but I'll investigate.

[keplersj]

Good thing this was linter-ruby. 😉

[steelbrain]

@k2b6s9j I am unable to repro. Can you make sure that you are on the latest version of atom?
This snippet executes without an error for me, does it produce an error for you?

a = atom.notifications.addError("some Error")
console.log(atom.views.getView(a))

[keplersj]

That snippet returns an atom-notification element in the console...

[steelbrain]

@k2b6s9j the code that's producing the error above, is the same code as this one. Probably that was a temporary weird error. Would you mind trying the linter-ruby thing again?

[keplersj]

Reloaded the window. Still happening.

[steelbrain]

@k2b6s9j does this work? #2

[keplersj]

How do I point NPM to that revision?

[steelbrain]

Well, you clone the repo in node_modules folder and checkout that branch

[keplersj]

Ah. Thanks.

[keplersj]

ReferenceError: packageName is not defined
    at /Users/kepler/.atom/packages/linter-ruby/node_modules/atom-package-deps/lib/view.js:17:70

[steelbrain]

@k2b6s9j just pushed. Pull it and try again.

[keplersj]

Error no longer occurs. It now shows an Info notification, with a progress bar. But the progress bar doesn't seem to be making any progress. However, APM installs have always been kinda slow for me, I'll give it a minute or two.

[keplersj]

[keplersj]

Okay. It's making no indication of any progress.

[steelbrain]

@k2b6s9j the progress bar doesn't make any progress for one package, it's like 0% to 100% at once because apm doesn't report it's install progress. However if you have more than one dependencies, then it'll mark one package installed as a progress point. I think I'll make the progress bar animate a bit.

[keplersj]

Okay.

[keplersj]

I think the install has stalled @steelbrain it still hasn't moved.

[steelbrain]

@k2b6s9j can you check if linter-ruby exists in ~/.atom/packages?
There's no reason for it to be stalled, it worked fine for me on the first run 😛
But yes, we do need Unit Tests.

[keplersj]

linter-ruby exists in ~/.atom/packages, linter does not. I'll restart Atom though and see if that works.

[keplersj]

Still not installing.

[steelbrain]

@k2b6s9j writing unit tests. Give me a few minutes.

[keplersj]

Awesome. Alright.

[steelbrain]

A confirmed fix is in v2.0.1