October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23182: ------------------------------------------ [~bdshadow] I tend to think that we should apply the current PR to centralize the "wrong" approach that we're currently using (to a single method) and remove the possibility of a NPE at the same time. In the next spring we then could implement your cleaner solution. Agree? > NullPointerException in PodLogsHandler.handleEvent > -------------------------------------------------- > > Key: JBIDE-23182 > URL: https://issues.jboss.org/browse/JBIDE-23182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Labels: openshift_v3, pod_log_console > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46) > at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-930) Create a fuse test for verifying generated IDs

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-930: --------------------------------------- Summary: Create a fuse test for verifying generated IDs Key: JBTIS-930 URL: https://issues.jboss.org/browse/JBTIS-930 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.2.Final Reporter: Andrej Podhradsky Assignee: Tomáš Sedmík There was a bug (FUSETOOLS-2061) which caused that an ID is generated also for non-camel elements. Please create a test which verify whether the ID is generated for correct elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23182 at 10/13/16 9:41 AM: -------------------------------------------------------------------- [~bdshadow] nice catch, I'm not all sure but your suggestion sounds about right. Reading your suggestion - which I tend to agree on - you'd replace the current PR with a "proper" solution that sets a child context, right? was (Author: adietish): [~bdshadow] nice catch, I'm not all sure but your suggestion sounds about right. > NullPointerException in PodLogsHandler.handleEvent > -------------------------------------------------- > > Key: JBIDE-23182 > URL: https://issues.jboss.org/browse/JBIDE-23182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Labels: openshift_v3, pod_log_console > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46) > at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23182) NullPointerException in PodLogsHandler.handleEvent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23182?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23182: ------------------------------------------ [~bdshadow] nice catch, I'm not all sure but your suggestion sounds about right. > NullPointerException in PodLogsHandler.handleEvent > -------------------------------------------------- > > Key: JBIDE-23182 > URL: https://issues.jboss.org/browse/JBIDE-23182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Labels: openshift_v3, pod_log_console > Fix For: 4.4.2.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.ui.handler.PodLogsHandler.handleEvent(PodLogsHandler.java:46) > at org.jboss.tools.openshift.internal.ui.handler.AbstractOpenShiftCliHandler.execute(AbstractOpenShiftCliHandler.java:70) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1) > at java.lang.reflect.Method.invoke(null:-1) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > {noformat} > Bundles: > | org.eclipse.e4.core.di | 1.6.0.v20160319-0612 | 1.6.0.v20160319-0612 | > | org.eclipse.ui | 3.108.0.v20160518-1929 | 3.108.0.v20160518-1929 | > | org.jboss.tools.openshift.ui | 3.3.0.v20160831-0703 | 3.3.0.v20160831-0703 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57d6df25e4b0fd7621...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-929?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-929: ---------------------------------- [~lhein] - please take a quick look at this issue - I'm not sure how the getting started interfaces into Central > Fuse project starter is available in Central only if we check EarlyAccess > ------------------------------------------------------------------------- > > Key: JBTIS-929 > URL: https://issues.jboss.org/browse/JBTIS-929 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 9.0.2.GA > Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA > Reporter: Andrej Podhradsky > > Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23122) use latest locus 1.6 bits from origin-nexus on http (avoid load balancer issues and cipher problems)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23122?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23122. -------------------------------- Verified in git. Commit was merged to 4.61.x. > use latest locus 1.6 bits from origin-nexus on http (avoid load balancer issues and cipher problems) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-23122 > URL: https://issues.jboss.org/browse/JBIDE-23122 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM2 > > > Switch from: > {code} > - <repository location="https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo..."/> > {code} > To: > {code} > + <repository location="http://origin-repository.jboss.org/nexus/content/unzip/unzip/org/jboss/to..."/> > {code} > This should avoid three problems: > a) disparate version of Locus (1.3 vs. 1.6 in integration stack) > b) origin-nexus vs. nexus avoid load balancer issues > c) http vs. https avoids cipher issues -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23307) Provide a menu in Forge view to trigger the forge wizard

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23307?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23307. --------------------------------- Button is implemented and is working. Closing. Verified in: Version: 10.2.0.AM2 Build id: AM2-v20161013-0009-B6197 Build date: 20161013-0009 > Provide a menu in Forge view to trigger the forge wizard > -------------------------------------------------------- > > Key: JBIDE-23307 > URL: https://issues.jboss.org/browse/JBIDE-23307 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: George Gastaldi > Labels: new_and_noteworthy, usability > Fix For: 4.4.2.AM2 > > Attachments: Screenshot from 2016-10-10 15-04-15.png > > > Having to guess the first time and then to remind the Ctrl+4 shortcut is just impossible. > please provide a menu in Forge view to trigger the action to open the wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-929: --------------------------------------- Summary: Fuse project starter is available in Central only if we check EarlyAccess Key: JBTIS-929 URL: https://issues.jboss.org/browse/JBTIS-929 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution, Fuse IDE Affects Versions: 9.0.2.GA Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA Reporter: Andrej Podhradsky Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4095) unparseable date in o.j.t.foundation.checkup

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4095?page=com.atlassian.jira.plugin.... ] Dmitrii Bocharov reassigned JBDS-4095: -------------------------------------- Assignee: Dmitrii Bocharov (was: Rob Stryker) > unparseable date in o.j.t.foundation.checkup > -------------------------------------------- > > Key: JBDS-4095 > URL: https://issues.jboss.org/browse/JBDS-4095 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation > Affects Versions: 10.2.0.AM1 > Environment: {code} > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160923-1714-B6096 > Build date: 20160923-1714 > $➔ uname -a > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1 > $➔ java -version > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Attachments: unparesable-date.png > > > Just started up devstudio 10.2.0.AM1-v20160923-1714-B6096 and got this error: > {code} > Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > java.text.ParseException: Unparseable date: "Thu Oct 06 13:55:38 EDT 2016" > at java.text.DateFormat.parse(DateFormat.java:366) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.getSessionDate(JVMProblemDetector.java:677) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.scanLine(JVMProblemDetector.java:240) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.readLogFile(JVMProblemDetector.java:186) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:118) > at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:77) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:53) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2829) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-925) Switch master branch to Neon (jbtis-4.4.x)

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/JBTIS-925?page=com.atlassian.jira.plugin.... ] Tomas David commented on JBTIS-925: ----------------------------------- Confirm. I changed my jbdsis9.x jenkins jobs to jbtis-4.3.x branch. > Switch master branch to Neon (jbtis-4.4.x) > ------------------------------------------ > > Key: JBTIS-925 > URL: https://issues.jboss.org/browse/JBTIS-925 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomáš Sedmík > Assignee: Andrej Podhradsky > Priority: Critical > > Our tests in master branch are still based on Mars (jbtis-4.3.x). Please switch master branch to Neon (jbtis-4.4.x) and preserve state of master branch in jbtis-4.3.x branch. > + update RedDeer from 1.0.2 to 1.1.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

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 October 2016