[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3682:
-----------------------------
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3682:
--------------------------------
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3682:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3682:
-----------------------------
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by Denis Golovin (JIRA)
Denis Golovin created JBDS-3682:
-----------------------------------
Summary: Online installer reports missing package.js file
Key: JBDS-3682
URL: https://issues.jboss.org/browse/JBDS-3682
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
Right way to reference package json would be:
{code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[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 edited comment on JBDS-3671 at 3/15/16 11:42 PM:
---------------------------------------------------------------
cygwin setup was removed and I have not restored it yet. I'll do it ASAP today, so I can point you out to the source. In short it does .msi setup as external process and then run shell script to add cygwin/bin to PATH. Here the [link to the version|https://github.com/redhat-developer-tooling/developer-platform-in...] before it was replaced with mingw.
Silent cygwin setup issue is JBDS-3632, it supposed to run msi as it does but without ui at all and use downloaded repository with packages. it means we still use the same command line, but with couple more options.
was (Author: dgolovin):
cygwin setup was removed and I have not restored it yet. I'll do it ASAP today, so I can point you out to the source. In short it does .msi setup as external process and then run shell script to add cygwin/bin to PATH. Here the [link to the version|https://github.com/redhat-developer-tooling/developer-platform-in...] before it was replaced with mingw.
Silent cygwin setup issue is JBDS-3632, it supposed to run msi as it does but without ui at all and use downloaded repository with packages. it means we still use the same command line, but with couple more options.
> 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
[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:
-------------------------------------
Mimicked all the steps and got the same message about fun. All questions seems can be answered with corresponding options (see below) but we always can try pipe input with < textfile
{code} echo "usage: ${progname} [OPTION]..."
echo
echo "This script creates an OpenSSH host configuration."
echo
echo "Options:"
echo " --debug -d Enable shell's debug output."
echo " --yes -y Answer all questions with \"yes\" automatically."
echo " --no -n Answer all questions with \"no\" automatically."
echo " --cygwin -c <options> Use \"options\" as value for CYGWIN environment var."
echo " --name -N <name> sshd windows service name."
echo " --port -p <n> sshd listens on port n."
echo " --user -u <account> privileged user for service, default 'cyg_server'."
echo " --pwd -w <passwd> Use \"pwd\" as password for privileged user."
echo " --privileged On Windows XP, require privileged user"
echo " instead of LocalSystem for sshd service."
echo
exit 1
;;{code}
and it should be executed in cygwing bash or run commands.
> 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
[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21802:
---------------------------------------
This happens because we are trying to get the metadata for an image and since we have content assist that triggers a fetch of metadata after a delay, it is asking the server to get this info. It obviously does not exist since the user has not completed the full docker image uri. Maybe we should consider adding a 'fetch' button that once the uri has been confirmed to exist by one of the methods (local, dockerhub, imagestreamimport), only then allows you to continue.
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21802
> URL: https://issues.jboss.org/browse/JBIDE-21802
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21869:
---------------------------------------
[~ncdc] We are shelling out to the OC binary and just pulling the Process outputstream. Do you know if there is anything in particular we can do to control the encoding?
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21449) WatchManager makes multiple callbacks for same event
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21449?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21449:
---------------------------------------
[~fbricon] First think to verify you dont get multiple callbacks is to allow the WatchClient to reconnect at least once. Then, you will probable need to do a conditional break on the 'received' of the listener to validate you are getting a single event. The code now applies a single listener per kind per project. Also, some actions will trigger multiple event callbacks but these are actually because the resource is being changed multiple times by the server.
> WatchManager makes multiple callbacks for same event
> ----------------------------------------------------
>
> Key: JBIDE-21449
> URL: https://issues.jboss.org/browse/JBIDE-21449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years