8000 SIGTTIN error while forking nteract app · Issue #2582 · nteract/nteract · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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

SIGTTIN error while forking nteract app #2582

Closed
szymonmaszke opened this issue Feb 23, 2018 · 7 comments
Closed

SIGTTIN error while forking nteract app #2582

szymonmaszke opened this issue Feb 23, 2018 · 7 comments
Labels
nteract-cli outdated workflow: issue should stay closed stale workflow: stale issue

Comments

@szymonmaszke
Copy link

  • OS: Arch Linux

  • Behaviour: Crashes nteract and parent process

  • Why: Detached nteract tries to read input from terminal (why would it do that? Jupyter notebook starts normally using procedure described below)

  • Required to replicate: Neovim, AUR package (https://aur.archlinux.org/packages/nteract-bin/)

How to reproduce: start neovim and type in:

:call jobstart('nteract')

Results: Neovim crashes, shell returns SIGTTIN, nteract fails to start.

Some additional informations:

  • terminal: Termite
  • using tmux?: yes, true color support
szymonmaszke pushed a commit to szymonmaszke/vimpyter that referenced this issue Feb 23, 2018
Add flags for notebooks, fix proxy in /tmp (correct naming)
06ec5c8 
Workarounds needed:
- set syntax as python (until this plugin provides new syntax file)

Problems:
- Name of create view can be a little too long and unreadable
- Starting nteract may not work correctly with nvim's jobstart (see: nteract/nteract#2582)
@rgbkrk
Copy link
Member
rgbkrk commented Feb 23, 2018

Oh interesting. Thanks for reporting. I don't know what's reading from stdin.

@szymonmaszke
Copy link
Author

Is there any chance for fixing this issue? I wanted to incorporate your app into my plugin but this bug is blocking me.

BTW. Sometimes this bug does not appear, but I can see no underlying cause as the command stays the same.

@rgbkrk
Copy link
Member
rgbkrk commented Feb 24, 2018

I'm sure we can figure it out together.

Curiosity -- what's your plugin for?

@szymonmaszke
Copy link
Author

Vim/Neovim integration with notebooks. Basics are ready but it would be nice to have support for your app before first release.

@stale
Copy link
stale bot commented Aug 24, 2018

This issue hasn't had any activity on it in the last 90 days. Unfortunately we don't get around to dealing with every issue that is opened. Instead of leaving issues open we're seeking to be transparent by closing issues that aren't being prioritized. If no other activity happens on this issue in one week, it will be closed.
It's more than likely that just by me posting about this, the maintainers will take a closer look at these long forgotten issues to help evaluate what to do next.
If you would like to see this issue get prioritized over others, there are multiple avenues 🗓:

  • Ask how you can help with this issue 👩🏿‍💻👨🏻‍💻
  • Help solve other issues the team is currently working on 👨🏾‍💻👩🏼‍💻
  • Donate to nteract so we can support developers to work on these features and bugs more regularly 💰🕐

Thank you!

@stale stale bot added the stale workflow: stale issue label Aug 24, 2018
@stale stale bot closed this as completed Aug 31, 2018
@rgbkrk rgbkrk reopened this Sep 4, 2018
@stale stale bot removed the stale workflow: stale issue label Sep 4, 2018
@rgbkrk
Copy link
Member
rgbkrk commented Sep 4, 2018

Re-opening as I think this is still good to go after -- we still need a great command line interface for nteract. Nothing is being invested in this area at the moment and we need help. 😄

@stale
Copy link
stale bot commented Oct 14, 2019

This issue hasn't had any activity on it in the last 90 days. Unfortunately we don't get around to dealing with every issue that is opened. Instead of leaving issues open we're seeking to be transparent by closing issues that aren't being prioritized. If no other activity happens on this issue in one week, it will be closed.
It's more than likely that just by me posting about this, the maintainers will take a closer look at these long forgotten issues to help evaluate what to do next.
If you would like to see this issue get prioritized over others, there are multiple avenues 🗓:

  • Ask how you can help with this issue 👩🏿‍💻👨🏻‍💻
  • Help solve other issues the team is currently working on 👨🏾‍💻👩🏼‍💻
  • Donate to nteract so we can support developers to work on these features and bugs more regularly 💰🕐

Thank you!

@stale stale bot added the stale workflow: stale issue label Oct 14, 2019
@stale stale bot closed this as completed Nov 14, 2019
@lock lock bot added the outdated workflow: issue should stay closed label Feb 13, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Feb 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
nteract-cli outdated workflow: issue should stay closed stale workflow: stale issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rgbkrk @willingc @szymonmaszke
0