Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Error: Unhandled Exception: End_Of_File #131

Open
tomitrescak opened this issue Aug 17, 2016 · 11 comments
Open

Error: Unhandled Exception: End_Of_File #131

tomitrescak opened this issue Aug 17, 2016 · 11 comments
Labels

Comments

@tomitrescak
Copy link

Hi, I keep receiveing following error quite often:

Error: Unhandled exception: End_of_file
    at ChildProcess.<anonymous> (/Users/tomi/.atom/packages/linter-flow/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:41:20)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:477:12)

I have mixed javascript and typescript files. Any idea what could be the problem?

@Arcanemagus
Copy link
Member

Do you consistently see this? Are you able to share the files you see this on if so?

@nmn
Copy link
Contributor

nmn commented Sep 24, 2016

Funnily, I started getting these errors recently too. But from a linter-eslint.

@bgeihsgt
Copy link

@Arcanemagus here's a file I'm consistently seeing this on:

// @flow
import chai from 'chai';
const expect = chai.expect;

import {
  authenticate,
  createAgent
} from '../../../fixtures';

describe('Foo, function() {

  let agent, user;

  beforeEach(async function() {
    agent = await createAgent();
    user = await authenticate(agent);
  });

});

Callstack:

Error: Unhandled exception: End_of_file
    at ChildProcess.<anonymous> (/Users/briangeihsler/.atom/packages/linter-flow/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:41:20)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:477:12)

@bgeihsgt
Copy link

It pops up regularly any time I'm typing. I need to disable the package when working in certain files :/

@nmn
Copy link
Contributor

nmn commented Sep 30, 2016

I think this is an issue with the linter package itself. Ive seen this error on and off in both linter-flow and linter-eslint.

@bgeihsgt
Copy link

@nmn If that was the case, then why would the problem go away when I disable linter-flow but keep linter-eslint on?

@nmn
Copy link
Contributor

nmn commented Oct 3, 2016

@bgeihsgt I don't know. I'm just reporting what I've experienced personally.

Lately, I can't reproduce the error at all. But if you could open up the console when you see this error and send us the stack trace that would be very helpful.

@bgeihsgt
Copy link

bgeihsgt commented Oct 5, 2016

@nmn I opened up the console and repro'd the red box but saw nothing on the console. Is the strack trace from the red box not sufficient?

Error: Unhandled exception: End_of_file
    at ChildProcess.<anonymous> (/Users/briangeihsler/.atom/packages/linter-flow/node_modules/atom-linter/node_modules/sb-exec/lib/index.js:41:20)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:477:12)

@Arcanemagus
Copy link
Member

Unfortunately the only part of that stack trace that means anything is Unhandled exception: End_of_file, which is coming from the stderr output of the command (flow). Why flow is returning that is the question...

@nmn I've yet to see a report on linter-eslint that shows that, are you sure it's not just flow running on the same files and hitting the same thing?

@Arcanemagus
Copy link
Member

Possibly related to facebook/flow#1693, it looks like there are a few different issues over there related to this message.

@jbmorgado
Copy link

I'm still receiving this error on atom while using linter-flow. On VSCode with Flow Language Support module, it works fine.

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

No branches or pull requests

5 participants