[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3671:
-------------------------------------
Yes this pacman worked for me and sshd -h would print out help text.
> sshd needs to be installed and started
> --------------------------------------
>
> Key: JBDS-3671
> URL: https://issues.jboss.org/browse/JBDS-3671
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Hardy Ferentschik
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container.
> docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues.
> An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that
> * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg...
> * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH
> I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach.
> Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21791:
-----------------------------------------------
org.jboss.tools.common.ui.dialog.CheckboxMessageDialog
> Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21791
> URL: https://issues.jboss.org/browse/JBIDE-21791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.1.Beta2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 4.3.1.CR1
>
> Attachments: eclipse-add.png
>
>
> Similar problem as FORGE-2605 but this time its in Eclipse.
> See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog.
> I wonder if the fix should be like in IDEA to save the file before the command is run.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21836) openshift 3 oc locaiton resets to a different/old value on restart
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21836:
-------------------------------------
there's a good possibility that might be caused by the OOMPH preference recorder. That recorded that value a long time ago and it now sets it to all new workspaces
> openshift 3 oc locaiton resets to a different/old value on restart
> ------------------------------------------------------------------
>
> Key: JBIDE-21836
> URL: https://issues.jboss.org/browse/JBIDE-21836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Blocker
>
> on start of eclipse new workspace the value is for reason unknown to me set to:
> {code}
> /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc
> {code}
> which does exist, but is old version and publish fails.
> Then I set it to
> {code}
> /usr/local/bin/oc
> {code}
> now publish works.
> Restart eclipse - old value returns and publish starts failing again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21828:
-----------------------------------------------
One more thought. Now, the content provider for Explorer is playing the role of the model that manages loading so that any time when viewer refresh triggered loading, events from the loading need to call refresh of viewer but it may cause looping.
The solution is to separate the model entirely from the content provider. Model should live independently and
- fulfil queries of its clients one of which is the content provider;
- refresh itself when requested in the manner I described in my previous comment;
- send events to clients.
The content provider will always receive the current state of model, when the model finds that an object is to loaded, it may put a flags on it like isOutOfSync(), isLoading(), etc, and execute
- loading _new_ substructure;
- merge to _current_ substructure;
- firing _one_ event with tree of changes.
Meanwhile, the content provider seeing that the object for which it is requested by the viewer to provide children, has isOutOfSync() = true or isLoading() = true, may return at its own discretion a fake node 'Loading...'; the label provider may in some way mark 'out of sync' nodes; action handlers can check it and warn user in a message dialog, etc. Finally, when _one_ event comes from the model, the tree viewer will refresh itself from the most top node affected, receiving again the _current_ structure of the model, probably with some more nodes out of sync and/or loading, if in the mean time the local model got new change events from the remote model.
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21836) openshift 3 oc locaiton resets to a different/old value on restart
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-21836:
-------------------------------------------
Summary: openshift 3 oc locaiton resets to a different/old value on restart
Key: JBIDE-21836
URL: https://issues.jboss.org/browse/JBIDE-21836
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Priority: Blocker
on start of eclipse new workspace the value is for reason unknown to me set to:
{code}
/Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc
{code}
which does exist, but is old version and publish fails.
Then I set it to
{code}
/usr/local/bin/oc
{code}
now publish works.
Restart eclipse - old value returns and publish starts failing again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ]
George Gastaldi commented on JBIDE-21791:
-----------------------------------------
Hi [~akazakov],
Do you have an example of how the "Don't ask again" option is implemented so I can try to reuse it? I managed to implement it asking for confirmation but I am not sure how should I display this "Don't ask again" option using the Eclipse APIs.
Thank you!
> Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21791
> URL: https://issues.jboss.org/browse/JBIDE-21791
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.1.Beta2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 4.3.1.CR1
>
> Attachments: eclipse-add.png
>
>
> Similar problem as FORGE-2605 but this time its in Eclipse.
> See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog.
> I wonder if the fix should be like in IDEA to save the file before the command is run.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21828:
-----------------------------------------------
At refresh now deployment mapper flushes - removes all children, sending a lot of events, then creates new children sending again a lot of events. This is why tree is collapsed, at stripping the parent node of old children, it forgot about them and there 'expand' state, and receiving new children it does not recognize in them 'clones' of old children.
I would suggest the approach that I followed always in doing models for UI. At request to refresh a substructure of the model, new substracture is created internally in a silent manner, then merge like oldModelObject.merge(newModelObject, listOfChanges) is done; which matches objects in the current structure to objects in the new structure, and if match is found, it just passes merge deeper with these matching old-new objects, doing the best to avoid removing/creating objects in the current structure (e.g. if one object is to be removed and one is to be created and they both have not matches, we still can merge new object to the old!), and along the way collecting changes made during the merge in a listOfChanges object (it may also be tree-like). When merge is completed, _one_ event is sent with 'listOfChanges'. When the listener responsible for refreshing the tree viewer gets this one event, it is sufficient to run once viewer.refresh(parent) for the parent to all nodes affected, and because most children remain the same instances - tree will refresh smartly without collapsing nodes.
This is an UI-friendly solution, and it could be good to find a way to apply it to the openshift UI model.
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21828 at 3/8/16 2:29 PM:
-----------------------------------------------------------------------
I also think that when an instance DeploymentResourceMapper runs buildDeployments for the first time, it should not fire any events. Explorer has just for the first time requested the project for children, it will get it through the mapper, and that should be all to it. Now, in the initial creating and loading of deployments and resources cache, a lot of events is sent. They should not be sent at all rather than be grouped. Model object should be able to do initial loading silently, be returned as the whole and then have a listener attached to it to report further incremental changes.
was (Author: scabanovich):
I also think that when an instance DeploymentResourceMapper runs buildDeployments for the first time, it should not fire any events. Explorer has just for the first time requested the project for children, it will get it through the mapper, and that should be all to it. Now, in the initial creating and loading of deployments and resources cache, a lot of events is sent. They should not be sent at all rather than be grouped. Model object should be able to do initial loading silently, be returned as be whole and then have a listener attached to it to report further incremental changes.
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21828:
-----------------------------------------------
I also think that when an instance DeploymentResourceMapper runs buildDeployments for the first time, it should not fire any events. Explorer has just for the first time requested the project for children, it will get it through the mapper, and that should be all to it. Now, in the initial creating and loading of deployments and resources cache, a lot of events is sent. They should not be sent at all rather than be grouped. Model object should be able to do initial loading silently, be returned as be whole and then have a listener attached to it to report further incremental changes.
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month