Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start flow on networked directory #356

Closed
JonathanTroyer opened this issue Aug 9, 2019 · 3 comments
Closed

Failed to start flow on networked directory #356

JonathanTroyer opened this issue Aug 9, 2019 · 3 comments

Comments

@JonathanTroyer
Copy link

JonathanTroyer commented Aug 9, 2019

Freshly installed the extension and was promptly met with this error:

{
  "flowconfig": "\\\\dtc\\files\\TestMyCorp\\...\\.flowconfig",
  "flow": {
    "path": "c:\\Users\\u61jtro\\.vscode\\extensions\\flowtype.flow-for-vscode-1.3.0\\node_modules\\flow-bin\\flow-win64-v0.104.0\\flow.exe",
    "version": "0.104.0"
  },
  "serverStatus": {
    "state": "error",
    "message": "Failed to start flow\nError: (Failure\n  \"not localhost - file://dtc/files/TestMyCorp/...\")",
    "actions": [
      {
        "title": "Retry"
      }
    ]
  }
}

I've already searched for this particular error, and cannot find anything related to localhost that's been reported previously.

Using VS Code 1.37.0 1.38.1, with extension version 1.3.0 1.5.0. Thanks!

@Mayank1791989
Copy link
Contributor

I think flow doesn't support networked directory. Is flow status through terminal working for you?

@JonathanTroyer
Copy link
Author

JonathanTroyer commented Sep 16, 2019

Sorry about the late response. I'm actually using the bundled flow (work doesn't allow us yarn/npm 😭). Calling C:\Users\u61jtro\.vscode\extensions\flowtype.flow-for-vscode-1.5.0\node_modules\flow-bin\flow-win64-v0.107.0\flow.exe status gives

Unhandled exception: (Sys_error "\\\\dtc\\files: No such file or directory")
Raised by primitive operation at file "hack/utils/sys/path.ml", line 61, characters 5-22
Called from file "src/commands/commandUtils.ml", line 1223, characters 13-30
Called from file "src/commands/commandUtils.ml", line 1244, characters 10-60
Called from file "src/commands/statusCommands.ml", line 194, characters 15-46
Called from file "src/commands/commandUtils.ml", line 13, characters 4-32
Called from file "src/flow.ml", line 106, characters 4-21

Not sure how helpful that is.

@Mayank1791989
Copy link
Contributor

Mayank1791989 commented Sep 17, 2019

Looks like flow doesn't support your use case. Create issue in flow repo (https://github.com/facebook/flow).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants