search

benmatselby / atom-php-checkstyle

✅ [DEPRECATED] Checkstyle reporter for PHP, utilising phpcs, phpmd, php linter and php-cs-fixer
MIT License
21 stars 5 forks source link

Uncaught NotFoundError #18

Closed yriveiro closed 10 years ago

yriveiro commented 10 years ago

I'm having this message each time this package runs and found an error:

Uncaught NotFoundError: An attempt was made to reference a Node in a context where it does not exist.

A dev-tools window opens and when I try to close it, it's open again in loop mode.

If I disable the package this behavior doesn't happen,

benmatselby commented 10 years ago

Can you provide the config you have please.

yriveiro commented 10 years ago

My config for the package:

'php-checkstyle':
  'phpcsDisplayWarnings': true
  'phpPath': '/usr/local/bin/php'
  'shouldExecutePhpcs': false
  'phpcsExecutablePath': '/usr/local/bin/phpcs'
benmatselby commented 10 years ago

Struggling to reproduce this to be honest. What version of Atom do you have? Also, to note, you are running the linter and phpmd, but not phpcs, is that correct?

Can you provide more of the stack trace please, so I can see what lines within the plugin are triggering this.

primitive-type commented 10 years ago

I can confirm that I'm also experiencing this issue, but it's hard to isolate what exactly is causing it. Disabling the package does solve it, but when the package is enabled, the only pattern I can track down that will trigger this error for me is when I save a file twice in a row in rapid succession. Sometimes it happens if I leave about a second in between saves. This is only the case when I have the setting "Should Execute On Save" checked. If I uncheck that option, then the error goes away no matter what I do, as far as I can tell.

I will try digging deeper to see if I can figure it out.

I'm using Atom version 0.81.0. I'm running everything but phpmd. The particular line of code generating the error is in /Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:5825.

benmatselby commented 10 years ago

Thanks for extra information. I believe I have resolved this in 0.14.0. Please re-open the bug if this is not the case.

primitive-type commented 10 years ago

That seems to have done the trick! Thanks.