February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22362: ------------------------------------------ [~psrna] yes, the changes are applied in master and 4.4.x. But were reverted in 4.4.3.x at it caused some more problems. This PR: https://github.com/jbosstools/jbosstools-openshift/pull/1412 was merged into master. These changes are also in 4.4.x branch: https://github.com/jbosstools/jbosstools-openshift/commits/jbosstools-4.4.x - see pre-last commit in Feb 15, 2017. But it was reverted in 4.4.3.x branch: https://github.com/jbosstools/jbosstools-openshift/commits/jbosstools-4.4... - see pre-last commit. Hope, i've answered your question =) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22362: ------------------------------------ Master: https://github.com/jbosstools/jbosstools-openshift/commit/489803738841864... 4.4.x: https://github.com/jbosstools/jbosstools-openshift/commit/489803738841864... > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22362: ------------------------------------ [~dbocharov] So this should be fixed in 4.4.x and master branch and reverted in 4.4.3.x branch, right? Can you point me to the specific commit in 4.4.x or master which is fixing this issue. I cannot find it, but I may be missing it. Thx. > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23961: ------------------------------------- Sprint: (was: devex #128 February 2017) > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-482) NullPointerException when committing Docker image [EBZ#512582]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-482: --------------------------------------- Summary: NullPointerException when committing Docker image [EBZ#512582] Key: ERT-482 URL: https://issues.jboss.org/browse/ERT-482 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Environment: Windows 7 Eclipse: Neon.1a Release (4.6.1) 20161007-1200 Docker Tooling: 2.1.0.201609141916 Steps to reproduce: 1. Pull latest tomcat (Note: I have no other images or containers in my docker at this time) 2. Run image 3. Commit container 4. This NPE will be shown: An internal error occurred during: "Committing Container to Image". java.lang.NullPointerException at org.eclipse.linuxtools.internal.docker.ui.commands.CommitContainerCommandHandler$1.run(CommitContainerCommandHandler.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) After this error happened, I restarted my workspace and tried to commit the container again and this time it worked. So it is possible that this happens because I have no images or containers on my docker. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4285) migrate jbosstools-releng view jobs to CCI

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4285: -------------------------------- Summary: migrate jbosstools-releng view jobs to CCI Key: JBDS-4285 URL: https://issues.jboss.org/browse/JBDS-4285 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: build Affects Versions: 10.3.0.GA Reporter: Nick Boldt migrate jobs in https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... to CCI Jenkins: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23965?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23965. ------------------------------ Resolution: Done After some performance testing, switched to the 10.5.* IP and it's working better than before. > externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23965 > URL: https://issues.jboss.org/browse/JBIDE-23965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final, 4.4.4.AM1, 4.5.0.AM1 > > > Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24006: ---------------------------------- Summary: Wildfly server adapter does not report error and works inconsistently Key: JBIDE-24006 URL: https://issues.jboss.org/browse/JBIDE-24006 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.3.Final Reporter: Jeff MAURY Fix For: 4.4.4.AM2 If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work. Here is an except we've got from the customer: {noformat} I have an important update on this. I think it's mostly good news. I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict. I tried the same thing on Eclipse with exactly the same results. {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-23882: -------------------------------------- PR: https://github.com/jbdevstudio/jbdevstudio-qa/pull/124 Jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rpm_rh_c... [~nickboldt], could you please have a look and let me know whether you are satisfied? I have described how it works in job description, you can also review PR, if you want. Job is currently configured to run from my fork and all parameters predefined, so you can start it as is. Build #26 passed without errors, because I have used wrong regular expression which I am using for finding of errors in the eclipse log. Build #27 failed, because I fix that regular expression :) But I have used old RHSCL (alpha 1.1) where is problem with Lucene, so, it correctly detected problem. {code} !ENTRY org.eclipse.core.jobs 4 2 2017-02-22 10:11:38.697 !MESSAGE An internal error occurred during: "Repository registry initialization". !STACK 0 java.lang.ExceptionInInitializerError at org.apache.lucene.codecs.lucene40.Lucene40Codec.<init>(Lucene40Codec.java:52) {code} Now the build #28 is running, this test should use Devstudio 10.4 and last snapshot of RHSCL. I see that until now one test passed and one failed. I will check it tomorrow. Do you have any suggestions? Should I run this test only against jbosstools-discovery.earlyaccess_master repository (1) or also against another repositories like (2) and (3)? (1) https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... (2) https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c...<br> (3) https://devstudio.redhat.com/10.0/staging/updates/integration-stack/disco... Thanks! > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.AM1 > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4038) Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4038?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4038: -------------------------------- Story Points: 2 > Devsuite bundle installer fails to install/configure CDK component on path with non-ascii character > --------------------------------------------------------------------------------------------------- > > Key: JBDS-4038 > URL: https://issues.jboss.org/browse/JBDS-4038 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: Windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.3.0.GA > > > Default installation on Non-ASCII path fails to install/configure CDK. > Error from install log file: > Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute command vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" > Thu, 01 Sep 2016 11:19:25 GMT-INFO: cdk - Execute options { > "env": { > "ALLUSERSPROFILE": "C:\\ProgramData", > "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", > "CommonProgramFiles": "C:\\Program Files\\Common Files", > "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", > "CommonProgramW6432": "C:\\Program Files\\Common Files", > "COMPUTERNAME": "SOME-PC", > "ComSpec": "C:\\Windows\\system32\\cmd.exe", > "FP_NO_HOST_CHECK": "NO", > "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", > "HOMEDRIVE": "C:", > "HOMEPATH": "\\Users\\jbossqa", > "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", > "LOGONSERVER": "\\\\SOME-PC", > "NUMBER_OF_PROCESSORS": "2", > "OS": "Windows_NT", > "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;c:\\DevelopmentÅ uite\\cdk\\bin;c:\\DevelopmentÅ uite\\vagrant\\bin;c:\\DevelopmentÅ uite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;c:\\DevelopmentSuite\\cdk\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;;c:\\DevelopmentŠuite\\vagrant\\bin;c:\\DevelopmentŠuite\\cygwin\\bin;C:\\DevelopmentŠuite\\virtualbox\\", > "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", > "PROCESSOR_ARCHITECTURE": "AMD64", > "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", > "PROCESSOR_LEVEL": "6", > "PROCESSOR_REVISION": "3c01", > "ProgramData": "C:\\ProgramData", > "ProgramFiles": "C:\\Program Files", > "ProgramFiles(x86)": "C:\\Program Files (x86)", > "ProgramW6432": "C:\\Program Files", > "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", > "PUBLIC": "C:\\Users\\Public", > "SESSIONNAME": "Console", > "SystemDrive": "C:", > "SystemRoot": "C:\\Windows", > "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "USERDOMAIN": "Some-PC", > "USERNAME": "jbossqa", > "USERPROFILE": "C:\\Users\\jbossqa", > "VAGRANT_DETECTED_OS": "cygwin", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentŠuite\\cdk\\boxes" > } > Thu, 01 Sep 2016 11:19:25 GMT-ERROR: cdk - Error: Command failed: vagrant plugin install "c:\DevelopmentŠuite\cdk\plugins\landrush-1.1.2.gem" > <internal:gem_prelude>:1:in `require': cannot load such file -- rubygems.rb (LoadError) > from <internal:gem_prelude>:1:in `<compiled>' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017