"Flow is type checking"... Forever!

[stephen-last]

I'm running VS Code 1.28.2, flow-bin 0.82.0 installed locally, on Windows 7 Pro.

I'm trying to add Flow to an existing project (a Node command line app), which right now has 20 dependencies and 18 devDependencies (mostly Babel and ESLint). This has a file count of around 17,000 in node_modules.

I don't think this is unusual, and I would expect Flow to not have any problems with this project.

I'm trying to add type annotations to my first file and all I can see is:

Never-ending "Flow is type checking"... At the moment Flow is completely unusable.

What is it type checking..? Is there any way to see the files/code that it's currently type checking..?

It definitely isn't type checking my 3 lines of annotations, so it must be type checking within node_modules, is that right..? How long should it take..?

[ArmorDarks]

I'm also getting hard times making flow-for-vscode work on Windows (10 in my case). Though, Flow itself works through a CLI as intended.

[SergioMorchon]

The same happens to me :(
And there are a lot of flow processes with no CPU usage in the task manager.

[stephen-last]

@SergioMorchon

Same here on the processes, there's another issue for that: #287

Are you on Windows as well..?

[SergioMorchon]

@stephen-last Yes, Windows 10.
Looks like under some conditions, flow processes go orphans or similar, because I can see:

• A lot of flow processes in the Task manager, even after closing VSCode.
• All of them without using CPU.
• One of them with a considerable amounf of RAM compared to others that have the same lower RAM consumption (compared).
• If I kill one of the small-ram process, nothing happens.
• If I kill the larger one, then all the flow processes get killed in cascada.

And regarding VSCode flow plugin hanging forever:

• If I open VSCode having previously those process I mentioned before, then the flow status will be forever loading. If then I kill the flow process, then a new one will be automatically spawn, using CPU and raising RAM and the plugin will load ok.
• If I previously kill all the flow process, then VSCode flow plugin will load fine.

[stephen-last]

@SergioMorchon I'm seeing exactly what you describe as well.

I have two projects setup with Flow. I seem to get 3 processes for each (more when Flow is actually doing something), one using more memory just as you describe. When I switch projects, or exit VS Code, the processes are left, still consuming memory.

When I run TASKLIST /FI "IMAGENAME eq flow.exe*" I see:

Running npm run flow -- stop (with flow added to scripts in package.json) does kill all the flow processes related to that project.

So... It looks like there may be an issue with the flow.stopFlowOnExit setting then, as @richardtks says in issue #281.

[SergioMorchon]

This is my new friend

Get-Process -Name flow | Stop-Process

These issue is my Top 1 blocking issue that prevents me to use this plugin. Because:

• I can't rely on Flow type checking: it could be not working for an unknown amount of time, making me thinking that my code is ok when maybe it's not.
• Suddenly autocompletion gets broken.
• On this state, I can't use flow from the CLI in conjunction with the plugin. See Can't run flow in cmd when VS Code is open in Windows #260 and Can't run flow in cmd when VS Code is open in Windows facebook/flow#6592.
• The error marks (those red underlines over the text) keeps floating over the older code position, breaking completely the development experience.

[JoshRosenstein]

Ditto to @SergioMorchon experience bur was using Process Hacker 2 to to bulk Kill for certain vscode windows.

[Diggsey]

Same issue here - windows 10.

[JoshRosenstein]

think this is related to the closed #172 issue.

[JoshRosenstein]

Seems to be just a lack of windows support, which is disappointing. booted up second computer with Ubuntu and this extension works flawlessly, compared to working with the same projects Ive opened up on my windows PC. Sucks that in order to try to make development a bit easier, you must first choose an OS before choosing which choosing tool sets. If i didnt have the flexibility to switch to linux or mac and had to stay with windows (ei. company issued computer), i would probably lean more towards typescript..

Edit**:
Just saw #287 , so far i've seen 10 processes just opening and switching files, will continue watching once i start actually start working on things.

[Tolgor]

Same here, the extension is not usable :(
Windows 10

[cmtmc]

Windows 10, extension stops working unpredictably. On exiting VSCode several flow.exe are hanging. How can I use the extension? Thanks!

[cmtmc]

Win10, flow 0.145.0 hangs the same way as a year ago. Any news on this?