[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3841:
------------------------------------
Update:
https://access.redhat.com/articles/2360571
Ensure that you are logged in using an Administrator account. The Installer adds drivers and changes environment variables and therefore requires Administrator permissions. Using a non-Administrator account and using the Run as Administrator option is not recommended.
> Installer Sets Path for Wrong User
> ----------------------------------
>
> Key: JBDS-3841
> URL: https://issues.jboss.org/browse/JBDS-3841
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
> Priority: Critical
> Labels: user-docs
> Fix For: 10.1.0.GA
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Roland Grunberg edited comment on JBIDE-23039 at 8/30/16 10:30 AM:
-------------------------------------------------------------------
I haven't had time to test this out, but here are a few suggestions :
- Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag.
- Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash', or 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"}
was (Author: rgrunber):
I haven't had time to test this out, but here are a few suggestions :
- Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag.
- Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"}
> 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
> 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)
7 years, 10 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Roland Grunberg commented on JBIDE-23039:
-----------------------------------------
I haven't had time to test this out, but here are a few suggestions :
- Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag.
- Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"};
> 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
> 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)
7 years, 10 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Roland Grunberg edited comment on JBIDE-23039 at 8/30/16 10:06 AM:
-------------------------------------------------------------------
I haven't had time to test this out, but here are a few suggestions :
- Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag.
- Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"}
was (Author: rgrunber):
I haven't had time to test this out, but here are a few suggestions :
- Can you make sure that the command being launched (presumably 'vagrant up') does not get passed the '--machine-readable' flag. I think I saw it in your code, but it appears vagrant doesn't support both interaction through stdin and that flag.
- Can you try wrapping your Runtime.getRuntime().exec(..) call in 'bash -i' . So basically something like new String [] {"bash", "-i", "-c", "vagrant up"};
> 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
> 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)
7 years, 10 months
[JBoss JIRA] (JBIDE-23058) VPE RefreshOptionsTest are failing from time to time on Jenkins
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23058?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23058:
--------------------------------
Summary: VPE RefreshOptionsTest are failing from time to time on Jenkins (was: VPE RefreshOptionsTest are failing from time to time )
> VPE RefreshOptionsTest are failing from time to time on Jenkins
> ---------------------------------------------------------------
>
> Key: JBIDE-23058
> URL: https://issues.jboss.org/browse/JBIDE-23058
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.4.1.AM3
> Reporter: Ilya Buziuk
> Assignee: Rastislav Wagner
> Fix For: 4.4.2.AM1
>
>
> The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
> 1) on windows the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> 2) on rhel7 the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> Those tests were disabled as part of JBIDE-22884, need to figure out the reason of failures
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22653) Scale Pod: should get warned when scaling to 0
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-22653:
------------------------------------
I'll do it today or as the first thing in the morning tomorrow.
> Scale Pod: should get warned when scaling to 0
> ----------------------------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.1.Final
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23058) VPE RefreshOptionsTest are failing from time to time
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23058?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23058:
--------------------------------
Description:
The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
1) on windows the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
2) on rhel7 the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
Those tests were disabled as part of JBIDE-22884, need to figure out the reason of failures
was:
The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
1) on windows the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
2) on rhel7 the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
Those tests were disabled as part of
> VPE RefreshOptionsTest are failing from time to time
> -----------------------------------------------------
>
> Key: JBIDE-23058
> URL: https://issues.jboss.org/browse/JBIDE-23058
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.4.1.AM3
> Reporter: Ilya Buziuk
> Assignee: Rastislav Wagner
> Fix For: 4.4.2.AM1
>
>
> The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
> 1) on windows the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> 2) on rhel7 the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> Those tests were disabled as part of JBIDE-22884, need to figure out the reason of failures
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23058) VPE RefreshOptionsTest are failing from time to time
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23058?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23058:
--------------------------------
Description:
The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
1) on windows the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
2) on rhel7 the following tests are failing from time to time:
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
Those tests were disabled as part of
> VPE RefreshOptionsTest are failing from time to time
> -----------------------------------------------------
>
> Key: JBIDE-23058
> URL: https://issues.jboss.org/browse/JBIDE-23058
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.4.1.AM3
> Reporter: Ilya Buziuk
> Assignee: Rastislav Wagner
> Fix For: 4.4.2.AM1
>
>
> The following tests are failing from time to time on Jenkins (was not able to reproduce locally) https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...
> 1) on windows the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.norefreshTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> 2) on rhel7 the following tests are failing from time to time:
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> org.jboss.tools.vpe.preview.editor.test.editor.RefreshOptionsTest.refreshOnSaveTest
> Those tests were disabled as part of
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22653) Scale Pod: should get warned when scaling to 0
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22653:
------------------------------------------
[~rhopp] Could you pelase verify my PR (integration tests are in the doing)?
> Scale Pod: should get warned when scaling to 0
> ----------------------------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.1.Final
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months