Open markmiro opened 8 years ago
I thought it might have been due to me using a self-built version of Atom (which was stuck at an older version), but it still fails with a standard install with version 1.1.0
@markmiro Does this happen on any remote file, or just JavaScript?
@scv119 this looks like an error in the generated service framework code. Any ideas?
@nmote Experiencing the same error here, fresh install of both Atom and Nuclide.
The error is being thrown from the nuclide-flow package, FlowService.js line 79. It seems to happen on Javascript code only.
@nmote Disabling the package fixed the issue. Disabled 70% of the nuclide-*
packages while at it and that dramatically increased the performance, things are smooth all the sudden. Those should not install by default, imho.
@nmote I uninstalled nuclide since it was causing a lot of lag while typing even on local files, but I don't remember the errors popping up on anything except JavaScript.
I'm running Atom 1.0.7-0a6da38 with Nuclide 0.0.32 on a 2015 retina macbook pro with El Capitan.
I get this error on key press after opening a remote file and starting to type anything. I keep seeing more instances of the notification that shows the error as I keep typing.