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

electrode development process exits periodically while editing files #1555

Closed
cdaringe opened this issue Mar 10, 2020 · 3 comments
Closed

electrode development process exits periodically while editing files #1555

cdaringe opened this issue Mar 10, 2020 · 3 comments

Comments

@cdaringe
Copy link
Contributor

cdaringe commented Mar 10, 2020

Type of issue

🐛 bug

My environment

OS version/details: osx, mojave
Node version: 12
npm version: 6
Version of yo : n/a

Expected behavior

  • error messages streamed to logs--not process crashes--when editing files

Current behavior

  • process crashes, leaves zombie behind on port 3000, exits back to calling shell process

Steps to reproduce the behavior

  • clone <internal-project>
  • npx clap dev
  • edit files! quickly?
  • observe process crash. observe zombie PID

suffers additional symptom discussed in #1552

Command line output

 Execution Failed - Errors: 
 1  cmd "node "/Users/c0d01a5/src/storks/node_modules/@xarc/app-dev/lib/dev-admin"  --exec "/Users/c0d01a5/src/storks/node_modules/@xarc/app/support/babel-run" --ext js,jsx,json,yaml,log,ts,tsx --watch config src/server -- src/server" exit code null
    at ChildProcess.<anonymous> (/Users/c0d01a5/src/storks/node_modules/xclap/lib/xqtor.js:477:23)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1028:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
@jchip
Copy link
Member

jchip commented Apr 28, 2020

could you please submit internal ticket with more info on this?

@jchip
Copy link
Member

jchip commented Apr 28, 2020

we fixed a number of issues that may be related during beta. I would like to test it on latest if you have the internal-project.

@cdaringe
Copy link
Contributor Author

cdaringe commented May 2, 2020

Repro is tricky on this one too, otherwise I would have liked to send a branch. I think my version is probably too far behind now to be viable. Perhaps if you guys have tried replicating and it's not happening, we can just close it

@jchip jchip closed this as completed Jul 21, 2020
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