Flow server error. #138

jdetle · 2018-09-08T23:46:14Z

Issue

Hi All, sorry if I can't help much which the log dump, but I'm trying to run yarn flow and getting this issue from the hack workers. Should I crosspost this in https://github.com/facebook/hhvm?

Error Dump

[2018-09-08 18:42:12.523] Initializing Server (This might take some time)
[2018-09-08 18:42:12.523] executable=/Users/mac/github/one/nteract.io/node_modules/flow-bin/flow-osx-v0.80.0/flow
[2018-09-08 18:42:12.523] version=0.80.0
[2018-09-08 18:42:12.525] Parsing
[2018-09-08 18:42:14.697] Building package heap
[2018-09-08 18:42:14.781] Loading libraries
[2018-09-08 18:42:16.505] Resolving dependencies
Exception: Failure("Str.replace: reference to unmatched group")
Potential backtrace:
Raised by primitive operation at file "str.ml", line 654, characters 2-54
Called from file "str.ml", line 679, characters 26-39
Called from file "str.ml", line 683, characters 31-51
Called from file "src/services/inference/module/module_js.ml", line 79, characters 21-111
Called from file "list.ml", line 96, characters 24-34
Called from file "src/services/inference/module/module_js.ml", line 89, characters 20-56
Called from file "src/state/locals/module/module_hashtables.ml", line 84, characters 17-23
Called from file "src/services/inference/module/module_js.ml", line 441, characters 21-63
Called from file "src/services/inference/module/module_js.ml", line 635, characters 2-79
Called from file "map.ml", line 294, characters 19-42
Called from file "src/services/inference/module/module_js.ml", line 642, characters 25-208
Called from file "src/services/inference/module/module_js.ml", line 673, characters 4-67
Called from file "src/services/inference/module/module_js.ml", line 683, characters 4-74
Called from file "src/services/inference/types_js.ml", line 187, characters 21-121
Called from file "list.ml", line 96, characters 24-34
Called from file "hack/procs/workerController.ml", line 189, characters 42-47
Called from file "hack/procs/worker.ml", line 103, characters 4-37
Worker exited (code: 2)
Subprocess(54327): fail 2Unhandled exception: Worker_failed (process_id = 54327): (Worker_quit WEXITED 2)
Raised at file "src/core/lwt.ml", line 3008, characters 20-29
Called from file "src/unix/lwt_main.ml", line 42, characters 8-18
Called from file "src/server/server.ml", line 157, characters 6-54

Versions

Version of flow-bin: '0.80.0'.
Yarn version: '1.9.4'

The text was updated successfully, but these errors were encountered:

jdetle · 2018-09-09T00:00:46Z

Sep  8 18:59:22.568 [info] Creating a new Flow server
Sep  8 18:59:23.474 [error] Closing connection 'some ephemeral connection' due to uncaught exception in read loop: End_of_file
Sep  8 18:59:23.474 [error] backtrace:
Sep  8 18:59:23.474 [error] Raised at file "map.ml", line 130, characters 10-25
Sep  8 18:59:23.474 [error] Called from file "src/core/lwt.ml", line 817, characters 20-60
Sep  8 18:59:23.474 [error] 
Sep  8 18:59:23.474 [error] Failed to shutdown socket client: Unix.Unix_error(Unix.ENOTCONN, "shutdown", "")
Sep  8 18:59:23.474 [error] backtrace:
Sep  8 18:59:23.474 [error] Raised by primitive operation at file "src/unix/lwt_unix.cppo.ml", line 1533, characters 2-38
Sep  8 18:59:23.474 [error] Called from file "src/monitor/socketAcceptor.ml", line 148, characters 18-49
Sep  8 18:59:23.474 [error] 
Unable to obtain kernel buffer: Operation not permitted
usage: sudo dmesg
Sep  8 18:59:28.011 [error] Flow server (pid 3686) exited with code Unknown_error (110)
Sep  8 18:59:28.011 [info] Monitor is exiting (Dying along with server)
Sep  8 18:59:28.011 [info] Broadcasting to threads and waiting 1 second for them to exit

more errors

jdetle · 2018-09-09T00:35:56Z

Closed because duplication of facebook/flow#5919, but this is a really difficult to debug error.

jdetle · 2018-09-10T13:21:50Z

Not sure if its the same issue so I'm going to leave this open for visibility

nrabinowitz · 2018-10-03T17:25:35Z

Seeing the same issue in v0.82.0:

Oct  3 10:19:24.763 [info] argv=/some_path/node_modules/flow-bin/flow-osx-v0.82.0/flow start
Oct  3 10:19:24.764 [info] Creating a new Flow server
Oct  3 10:20:03.298 [error] Closing connection 'server #1' due to uncaught exception in read loop: End_of_file
Oct  3 10:20:03.298 [error] backtrace:
Oct  3 10:20:03.298 [error] Raised at file "map.ml", line 130, characters 10-25
Oct  3 10:20:03.298 [error] Called from file "src/unix/lwt_engine.ml", line 318, characters 8-36
Oct  3 10:20:03.298 [error] 
Unable to obtain kernel buffer: Operation not permitted
usage: sudo dmesg
Oct  3 10:20:03.314 [error] Flow server (pid 74556) exited with code Unknown_error (110)
Oct  3 10:20:03.314 [info] Monitor is exiting (Dying along with server)
Oct  3 10:20:03.314 [info] Broadcasting to threads and waiting 1 second for them to exit

In my case, I suspect this to be due to the number of files Flow is trying to parse (running this from the root of a monorepo with 165K files including node_modules).

MarcelCutts · 2018-10-19T14:11:45Z

We've been seeing this failure on our CI too.

yarn run v1.9.2
$ flow check
Worker interrupted with signal: sigkill
Subprocess(108): fail 2Unhandled exception: Worker_failed (process_id = 108): (Worker_quit WEXITED 2)
Raised at file "src/core/lwt.ml", line 3008, characters 20-29
Called from file "src/unix/lwt_main.ml", line 42, characters 8-18
Called from file "src/commands/checkCommands.ml", line 108, characters 57-132
Called from file "src/flow.ml", line 86, characters 6-34

Worker slave 144 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 144 Potential backtrace:
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Worker slave 138 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 138 Potential backtrace:
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Worker slave 146 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 146 Potential backtrace:
Worker slave 150 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 150 Potential backtrace:
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
Worker slave 152 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 152 Potential backtrace:
Worker slave 151 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 151 Potential backtrace:
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Worker slave 149 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 149 Potential backtrace:
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Worker slave 147 exception: Unix.Unix_error(Unix.EPIPE, "write", "")
Worker slave 147 Potential backtrace:
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-312
Called from file "hack/utils/measure.ml", line 238, characters 12-16
Called from file "hack/procs/worker.ml", line 88, characters 14-143
Called from file "hack/procs/worker.ml", line 128, characters 4-37
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
error Command failed with exit code 110.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Unix.Unix_error(Unix.EPIPE, "write", "")
Raised by primitive operation at file "unix.ml", line 257, characters 7-34
Called from file "hack/utils/marshal_tools.ml", line 145, characters 6-67
Called from file "hack/utils/marshal_tools.ml", line 158, characters 4-63
Called from file "hack/utils/sys/timeout.ml", line 28, characters 12-18
Exited with code 1

jdetle · 2018-10-19T17:42:13Z

I may be full of it but I think it usually comes from a typo that leads to fatal error parsing flow

MarcelCutts · 2018-10-22T21:29:08Z

To be clear, it's not consistent for us. Rerunning the workflow on Circle usually does the trick.

travelerspb · 2018-11-14T01:59:10Z

we have the same issue (v0.84). On CircleCI only, never occurs on local machines

morloy · 2018-12-05T17:57:45Z

Same here. Never fails on local machines, fails 70% of the time on CircleCI.

* master: Do not run flow on CI until this is fixed: flow/flow-bin#138 Run one-off flow check instead of starting server/watcher. Upload flow logs to CI

* master: Do not run flow on CI until this is fixed: flow/flow-bin#138 Run one-off flow check instead of starting server/watcher. Upload flow logs to CI Try running flow separately?

psirenny · 2018-12-09T13:29:39Z

I ran into this issue when another script failed to terminate the flow server once it finished running. In my case, flow-coverage-report was the culprit.

* master: (64 commits) 🐈 upgrade deps Delist products/versions/plans. Unlisted versions can't be most recent version 🛢 merge migrations 🛢 Add missing migration. 📦 Upgrade github.py Update boto3 from 1.9.57 to 1.9.62 Update cumulusci from 2.2.2 to 2.2.3 Update service_identity from 17.0.0 to 18.1.0 Update channels from 2.1.5 to 2.1.6 Update newrelic from 4.6.0.106 to 4.8.0.110 🛢 Add is_listed boolean to Product/Plan/Version Order Products by Category, then order_key Do not run flow on CI until this is fixed: flow/flow-bin#138 Run one-off flow check instead of starting server/watcher. Upload flow logs to CI Try running flow separately? Separate Flow from ESLint. better? 🐈 Upgrade deps. ...

jesstelford · 2018-12-18T23:57:04Z

For those arriving here via google with CI (particularly CircleCI) failures; add the following:

.flowconfig

[options]
server.max_workers=1

This will stop flow from trying to consume too many virtual CPUs (which CircleCI doesn't actually provide), letting it run to completion without first running out of memory and killing its sub processes.

deterralba · 2018-12-28T14:28:44Z

Thanks @jesstelford. For circleCI, it also works with server.max_workers=4 and is probably faster.

Summary: Added `max_workers` limit to flow configuration to prevent CircleCI consuming too many resources. Found this solution after investigating CircleCI logs. Where we have similar errors as mentioned in this issue flow/flow-bin#138 with suggested solution.

LeoLeBras · 2019-04-16T13:36:54Z

In my case, I launched flow during yarn install with CircleCI :

{
  "scripts": {
    "prepublish": "yarn test && yarn build",
    "test": "eslint . && flow && jest --coverage --forceExit"
  },
}

I replaced prepublish with prepublishOnly to fix the problem.

flow/flow-bin#138 (comment) flow/flow-bin#138 (comment) > This will stop flow from trying to consume too many virtual CPUs (which CircleCI doesn't actually provide), letting it run to completion without first running out of memory and killing its sub processes. The log output in CircleCI was: https://circleci.com/gh/bvaughn/react-devtools-experimental/201 ``` #!/bin/bash -eo pipefail yarn flow yarn run v1.10.1 $ /home/circleci/repo/node_modules/.bin/flow Launching Flow server for /home/circleci/repo Spawned flow server (pid=259) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=361) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=464) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=567) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Lost connection to the flow server (0 retries remaining): -Out of retries, exiting! error Command failed with exit code 7. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Exited with code 1 ```

mroch · 2022-03-18T14:33:04Z

Closing out old issues. This repository is just packaging prebuilt binaries. Please report issues with Flow itself on facebook/flow

flow/flow-bin#138 (comment) flow/flow-bin#138 (comment) > This will stop flow from trying to consume too many virtual CPUs (which CircleCI doesn't actually provide), letting it run to completion without first running out of memory and killing its sub processes. The log output in CircleCI was: https://circleci.com/gh/bvaughn/react-devtools-experimental/201 ``` #!/bin/bash -eo pipefail yarn flow yarn run v1.10.1 $ /home/circleci/repo/node_modules/.bin/flow Launching Flow server for /home/circleci/repo Spawned flow server (pid=259) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=361) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=464) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Launching Flow server for /home/circleci/repo Spawned flow server (pid=567) Logs will go to /tmp/flow/zShomezScirclecizSrepo.log Monitor logs will go to /tmp/flow/zShomezScirclecizSrepo.monitor_log Lost connection to the flow server (0 retries remaining): -Out of retries, exiting! error Command failed with exit code 7. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Exited with code 1 ```

jdetle closed this as completed Sep 9, 2018

jdetle reopened this Sep 10, 2018

jgerigmeyer added a commit to SFDO-Tooling/MetaDeploy that referenced this issue Dec 6, 2018

Do not run flow on CI until this is fixed: flow/flow-bin#138

7ffdd32

jgerigmeyer mentioned this issue Dec 6, 2018

Skip running flow on CI for now SFDO-Tooling/MetaDeploy#138

Merged

This was referenced Dec 28, 2018

Flow sometimes crashes on Prepack facebook/flow#6242

Closed

Installation error node_modules/oboe/test/json/incomplete.json:2:1 facebook/flow#6235

Closed

JosefDuda mentioned this issue Feb 13, 2019

Fix: Fixed failing flow on CircleCI kiwicom/margarita#274

Merged

mourner mentioned this issue Mar 21, 2019

Fix Flow Circle CI failures, upgrade to v0.95.1 mapbox/mapbox-gl-js#8061

Merged

sompylasar mentioned this issue Apr 30, 2019

Fix Flow failure on CircleCI due to the number of workers bvaughn/react-devtools-experimental#247

Merged

superhawk610 mentioned this issue May 9, 2019

Experiment with Docz joshwcomeau/guppy#254

Open

cyrildurand added a commit to cyrildurand/calgary that referenced this issue Jun 6, 2019

update flowconfig max_workers to 4 for circleci. See flow/flow-bin#138

8ff0b77

jamesisaac mentioned this issue Sep 2, 2019

Flow crashes unpredictably on CircleCI facebook/flow#8058

Closed

LudvigHz mentioned this issue Nov 13, 2019

Change flow use max 4 workers so circleCI stops crashing 9/10 times itdagene-ntnu/itdagene-webapp#119

Merged

mroch closed this as completed Mar 18, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Flow server error. #138

Flow server error. #138

jdetle commented Sep 8, 2018 •

edited

Loading

jdetle commented Sep 9, 2018

jdetle commented Sep 9, 2018

jdetle commented Sep 10, 2018

nrabinowitz commented Oct 3, 2018

MarcelCutts commented Oct 19, 2018

jdetle commented Oct 19, 2018

MarcelCutts commented Oct 22, 2018

travelerspb commented Nov 14, 2018

morloy commented Dec 5, 2018

psirenny commented Dec 9, 2018

jesstelford commented Dec 18, 2018

deterralba commented Dec 28, 2018

LeoLeBras commented Apr 16, 2019

mroch commented Mar 18, 2022

Flow server error. #138

Flow server error. #138

Comments

jdetle commented Sep 8, 2018 • edited Loading

Issue

Error Dump

Versions

jdetle commented Sep 9, 2018

jdetle commented Sep 9, 2018

jdetle commented Sep 10, 2018

nrabinowitz commented Oct 3, 2018

MarcelCutts commented Oct 19, 2018

jdetle commented Oct 19, 2018

MarcelCutts commented Oct 22, 2018

travelerspb commented Nov 14, 2018

morloy commented Dec 5, 2018

psirenny commented Dec 9, 2018

jesstelford commented Dec 18, 2018

deterralba commented Dec 28, 2018

LeoLeBras commented Apr 16, 2019

mroch commented Mar 18, 2022

jdetle commented Sep 8, 2018 •

edited

Loading