[jbosstools-issues] [JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293660#comment-13293660 ] 

Rob Stryker commented on JBIDE-23039:
-------------------------------------

I tried changing it to PTY.Mode.CONSOLE instead of PTY.Mode.TERMINAL  but it just errored (no seg-fault, just normal IOException), and javadoc indicates the PTY.Mode.Console mode is not available on windows. 

However it also lists only linux_x86, linux_x86_64, solaris, and macosx as supported for PTY.Mode.TERMINAL..... ... so kinda mixed messages ;)  It's basically saying it "might" work on windows. 

As far as I can tell, my dev-env is segfaulting bc the native stuff isn't working correctly, probably because it's not a proper installation (but who knows for sure). 

So, summary:
1) This bug (right now) needs to fix linux and mac primarily. Things "mostly work" on windows... 
2) I still think it's a good idea to test this newest PR on windows anyway bc there's a chance it works and even if it doesn't fix the problem but at least doesn't crash, then it keeps the UI unified. 


So let's try to get this tested on mac and windows tomorrow (today?). 
https://github.com/jbosstools/jbosstools-openshift/pull/1312
- Rob

> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
>                 Key: JBIDE-23039
>                 URL: https://issues.jboss.org/browse/JBIDE-23039
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.4.1.AM2
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.4.2.AM1
>
>         Attachments: vagranttty.png
>
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. 
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted. 
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. 
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec.  The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. 
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
>    a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
>    b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view.  This solution fails requirements 1 and 2.  We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. 
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. 
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? 
> No other obvious solutions have presented themselves in the past year. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)