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.

Sign up for GitHub

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

Jump to bottom

Detect runtime errors in RPC remote processes and flag them #164

Open
bgribble opened this issue Jun 27, 2014 · 1 comment
Open

Detect runtime errors in RPC remote processes and flag them #164

bgribble opened this issue Jun 27, 2014 · 1 comment
Labels
bug

Comments

@bgribble
Copy link
Owner

For instance -- if the build process does not install a runtime dependency and the GUI process bombs, currently it will just hang indefinitely.
@bgribble bgribble added this to the mfp 0.05 milestone Jun 27, 2014
@bgribble bgribble added the bug label Jun 27, 2014
bgribble added a commit that referenced this issue Jul 2, 2014
@bgribble
GitHub #164: Test for imports at launch, start to improve errors in RPC
0b019e1
@bgribble bgribble removed this from the mfp 0.05 milestone Jul 2, 2014
@bgribble
Copy link
Owner Author

bgribble commented Jul 2, 2014

The above commit addresses the worst case (first run hangs indefinitely because python module not installed) but only makes a start on robustly handling unexpected errors in the remotes.

I'm going to remove this ticket from the 0.05 milestone since the worst pain is mitigated. It still needs more work for a future release.

@bgribble bgribble mentioned this issue Jul 2, 2014
Closed
bgribble added a commit that referenced this issue Jul 2, 2014
@bgribble
GitHub #164: Tighten up exit semantics to allow normal exits
7cbea57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bgribble