Column start (2) greater than line length (1) Error

[atomlinter]

Column start (2) greater than line length (1) Error

[Arcanemagus]

Not related, this is just a message that is returned from the common helper library when an invalid line/col is sent to it for generation of a range.

Looking into this now.

[Arcanemagus]

Hmmmm, I can't reproduce that with this setup: linter-stylelint_GH143.zip

Are you possibly not on the latest version of linter-stylelint? It looks like you've ran into issues before with stylelint-selector-bem-pattern.

[Arcanemagus]

.....and all of the issue content just disappeared???

[ismay]

@Arcanemagus Whoa, that's weird! I didn't edit it. I'm not at work now, so I can't reproduce the error, but I'll do so tomorrow and restore the original comment.

As for the version, I've done a fresh install of all the packages (even of atom), but maybe atom reused old packages after the reinstall? I'll try reinstalling the plugin, will let you know if that helps.

[Arcanemagus]

Even stranger, the audit log on the organization shows no record of the edit 😕

Anyway, the zip file contains the state of the configuration before it disappeared...

[Arcanemagus]

Looks like it was a bug with assigning the (ironically: bug) label: https://status.github.com/messages

Also apparently there is no audit log for the description, only comments.

[ismay]

Ah ok 😋

[Arcanemagus]

Were you able to reproduce this @ismay?

[ismay]

You mean after updating linter-stylelint right?

Are you possibly not on the latest version of linter-stylelint? It looks like you've ran into issues before with stylelint-selector-bem-pattern.

Yeah it did occur again periodically, not sure what's triggering it. I'll do some more isolated testing on monday while at work, which is where I'm running into this. Will report back with the results.

[ismay]

After some testing I'm no longer able to reproduce it. I think we can close this, should I encounter it again I'll let you know.

[Arcanemagus]

Okay, if you see it again immediately save the file in that state, run stylelint on it from a CLI and see if you can spot the line that is off and report it, we can work out where the issue is from there.