"Something went wrong internally, reopen and no worries"

[corysimmons]

atom/atom#14248

Happens really frequently for no discernible reason.

[damon-kreft]

Yeah same here. Consistently the the very first time I open Atom and my first JS file, whether standard is in devDependencies or not...

Here are my Atom settings/packages: https://gist.github.com/damon-kreft/9801de58dce368df4f06b917f317559a

[dcalhoun]

I can confirm this warning displays when opening the first JavaScript file after creating a new Atom window. It happens every time consistently. After the first JavaScript file is open, the warning does not appear again until I create a new Atom window (i.e. the warning does not display for the 2nd, 3rd, 4th, etc JavaScript file).

Environment

• Atom 1.16.0
• linter 2.1.4
• linter-ui-default 1.2.3
• linter-js-standard 3.9.0
• standard 10.0.1

[mattfysh]

I don't know enough about atom internals but it looks like this.cache.get('text-editor', ... inside of linter-js-standard.js is being trigger before the call to this.cache.set... in init.js

[dcalhoun]

This is a duplicate of #126 and should likely be closed.

[whaaaley]

@dcalhoun i think this issue differs because:

• it happens on just the first file opened
• only one error appears
• only happens after you start atom and open a file

[pablomayobre]

I had this same issue, as @whaaaley explained, it started to happen after my configuration was reset (for some other problem I'm guessing).

I cannot reproduce this consistently though

[revelt]

Confirmed, it's happening exactly as @whaaaley described. First open of first JS file. Subsequent opens won't trigger the error. I can recreate it, just close the window, open some project, click on the tree view on any JS file, error will appear.

It will appear again and again if you won't double-click-open one JS file and close it. After closing, it does not appear on that window any more.

[revelt]

Switching to an alternative Standard linter, linter-js-standard-engine solved this for me.

[whaaaley]

@revelt Looks nice, however it looks like everything is an error rather than having some warnings, but that's much more tolerable than a message window. I'll be using this from now on too.

[whaaaley]

@revelt Looks like that project doesn't have html support or support for a global install or a default engine... all of those things are kind of a bummer for me. I might go digging later and try to fix this.

[whaaaley]

Looks like the PR by @educcjr fixes this! I just cloned and tested it out.

[sonicdoe]

This will be fixed in an upcoming patch version.

[sonicdoe]

Released in v3.9.2 🎉

[revelt]

I can confirm 3.9.2 works perfectly. Thanks everybody!