[JBoss JIRA] (JBIDE-24492) Application wizard: Details for custom template are not shown until "Next" is pressed.
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24492:
-------------------------------------
Summary: Application wizard: Details for custom template are not shown until "Next" is pressed. (was: Details for custom template are not shown until "Next" is pressed.)
> Application wizard: Details for custom template are not shown until "Next" is pressed.
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-24492
> URL: https://issues.jboss.org/browse/JBIDE-24492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Radim Hopp
> Assignee: Josef Kopriva
> Priority: Major
> Labels: application_wizard
> Fix For: 4.10.0.AM1
>
>
> Almost certainly a regression caused by JBIDE-23473.
> I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem?
> Screencast: https://youtu.be/uGAmL_sMIXc
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-24492) Details for custom template are not shown until "Next" is pressed.
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24492 at 10/17/18 4:53 AM:
--------------------------------------------------------------------
[~jkopriva] Indeed, this is a regression of JBIDE-23473. JBIDE-23473 changed the code so that the template is only loaded when the page is up to get flipped over (*onPageWillGetDeactivated* doing the *model.loadAppSource*):
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dR805}
@Override
protected void onPageWillGetDeactivated(Direction progress, PageChangingEvent event, DataBindingContext dbc) {
if (model.isUseLocalAppSource()) {
String filename = model.getLocalAppSourceFileName();
if (StringUtils.isNotBlank(filename)) {
Job job = new Job(NLS.bind("Loading application source", filename)) {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
Before JBIDE-23473 the template was being loaded upon keystroke (*handleValueChange* doing the *model.loadAppSource*):
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dL825}
@Override
public void handleValueChange(ValueChangeEvent<? extends Object> event) {
if (model.isUseLocalAppSource()) {
if (StringUtils.isNotBlank(model.getLocalAppSourceFileName())) {
Job job = new Job("Loading application source") {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
was (Author: adietish):
[~jkopriva] Indeed, this is a regression of JBIDE-23473. JBIDE-23473 changed the code so that the template is only loaded when the page is up to get flipped over:
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dR805}
@Override
protected void onPageWillGetDeactivated(Direction progress, PageChangingEvent event, DataBindingContext dbc) {
if (model.isUseLocalAppSource()) {
String filename = model.getLocalAppSourceFileName();
if (StringUtils.isNotBlank(filename)) {
Job job = new Job(NLS.bind("Loading application source", filename)) {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
Before JBIDE-23473 the template was being loaded upon keystroke:
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dL825}
@Override
public void handleValueChange(ValueChangeEvent<? extends Object> event) {
if (model.isUseLocalAppSource()) {
if (StringUtils.isNotBlank(model.getLocalAppSourceFileName())) {
Job job = new Job("Loading application source") {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
> Details for custom template are not shown until "Next" is pressed.
> ------------------------------------------------------------------
>
> Key: JBIDE-24492
> URL: https://issues.jboss.org/browse/JBIDE-24492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Radim Hopp
> Assignee: Josef Kopriva
> Priority: Major
> Labels: application_wizard
> Fix For: 4.10.0.AM1
>
>
> Almost certainly a regression caused by JBIDE-23473.
> I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem?
> Screencast: https://youtu.be/uGAmL_sMIXc
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-24492) Details for custom template are not shown until "Next" is pressed.
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24492:
------------------------------------------
[~jkopriva] Indeed, this is a regression of JBIDE-23473. JBIDE-23473 changed the code so that the template is only loaded when the page is up to get flipped over:
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dR805}
@Override
protected void onPageWillGetDeactivated(Direction progress, PageChangingEvent event, DataBindingContext dbc) {
if (model.isUseLocalAppSource()) {
String filename = model.getLocalAppSourceFileName();
if (StringUtils.isNotBlank(filename)) {
Job job = new Job(NLS.bind("Loading application source", filename)) {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
Before JBIDE-23473 the template was being loaded upon keystroke:
{code:title=https://github.com/jbosstools/jbosstools-openshift/pull/1502/files#diff-518c8f0f0d3d47e02da65022370e7e9dL825}
@Override
public void handleValueChange(ValueChangeEvent<? extends Object> event) {
if (model.isUseLocalAppSource()) {
if (StringUtils.isNotBlank(model.getLocalAppSourceFileName())) {
Job job = new Job("Loading application source") {
@Override
protected IStatus run(IProgressMonitor monitor) {
model.loadAppSource(monitor);
return Status.OK_STATUS;
}
};
{code}
> Details for custom template are not shown until "Next" is pressed.
> ------------------------------------------------------------------
>
> Key: JBIDE-24492
> URL: https://issues.jboss.org/browse/JBIDE-24492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Radim Hopp
> Assignee: Josef Kopriva
> Priority: Major
> Labels: application_wizard
> Fix For: 4.10.0.AM1
>
>
> Almost certainly a regression caused by JBIDE-23473.
> I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem?
> Screencast: https://youtu.be/uGAmL_sMIXc
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26158) Server adapter: NPE when starting adapter into Debug
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26158?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26158 at 10/17/18 4:16 AM:
--------------------------------------------------------------------
The NPE occurs at the following code in the eclipse platform:
{code:title=org.eclipse.core.internal.resources.CheckMissingNaturesListener#updateRange}
FileUtil.transferStreams(input, output, file.getLocation().toString(), new NullProgressMonitor());
{code}
The culprit is
{code}
file.getLocation()
{code}
The file (<project-name>.project) has no location, but the project for it is accessible.
!image-2018-07-02-23-17-34-099.png!
The file that's being used (*L/nodejs-ex (1)/.project*) is in a project that the chromium tooling created behind the scenes. It is not visible in the project explorer but it is in the navigator (decorated with a chrome tools icon):
!image-2018-07-02-22-49-45-246.png!
This latter project is created and opened by the chromium tools in
{code:title=org.eclipse.wst.jsdt.chromium.debug.core.util.ChromiumDebugPluginUtil#createEmptyProject}
try {
project.create(description, null);
project.open(null);
return project;
} catch (CoreException e) {
ChromiumDebugPlugin.log(e);
return null;
}
{code}
*project.open(null)* causes the *CheckMissingNaturesListener* to check for the missing natures.
{code}
CheckMissingNaturesListener$3(InternalWorkspaceJob).<init>(String) line: 27
CheckMissingNaturesListener$3(WorkspaceJob).<init>(String) line: 63
CheckMissingNaturesListener$3.<init>(CheckMissingNaturesListener, String, Set, IProject, Set) line: 163
CheckMissingNaturesListener.updateMarkers(Collection<IProject>) line: 163
CheckMissingNaturesListener.resourceChanged(IResourceChangeEvent) line: 46
NotificationManager$1.run() line: 297
SafeRunner.run(ISafeRunnable) line: 42
NotificationManager.notify(ResourceChangeListenerList$ListenerEntry[], ResourceChangeEvent, boolean) line: 287
NotificationManager.broadcastChanges(ElementTree, ResourceChangeEvent, boolean) line: 150
Workspace.broadcastPostChange() line: 376
Workspace.endOperation(ISchedulingRule, boolean) line: 1499
Project.open(int, IProgressMonitor) line: 1098
Project.open(IProgressMonitor) line: 1107
ChromiumDebugPluginUtil.createEmptyProject(String) line: 143
VProjectWorkspaceBridge.<init>(String, ConnectedTargetData, JavascriptVm) line: 101
VProjectWorkspaceBridge$FactoryImpl.attachedToVm(ConnectedTargetData, JavascriptVm) line: 78
ConnectedTargetData.initWorkspaceRelations() line: 222
ConnectedTargetData.setVmEmbedder(JavascriptVmEmbedder) line: 85
DebugTargetImpl.attach(DebugTargetImpl, JavascriptVmEmbedder$ConnectionToRemote, DestructingGuard, Runnable, IProgressMonitor) line: 86
StandaloneV8LaunchType(LaunchTypeBase).launch(ILaunchConfiguration, String, ILaunch, IProgressMonitor) line: 101
LaunchConfigurationWorkingCopy(LaunchConfiguration).launch(String, IProgressMonitor, boolean, boolean) line: 859
LaunchConfigurationWorkingCopy(LaunchConfiguration).launch(String, IProgressMonitor, boolean) line: 717
DebugUIPlugin.buildAndLaunch(ILaunchConfiguration, String, IProgressMonitor) line: 1039
DebugUIPlugin$8.run(IProgressMonitor) line: 1256
Worker.run() line: 60
{code}
was (Author: adietish):
The NPE occurs at the following code in the eclipse platform:
{code:title=org.eclipse.core.internal.resources.CheckMissingNaturesListener#updateRange}
FileUtil.transferStreams(input, output, file.getLocation().toString(), new NullProgressMonitor());
{code}
The culprit is
{code}
file.getLocation()
{code}
The file (<project-nam>.project) has no location, but the project for it is accessible.
!image-2018-07-02-23-17-34-099.png!
The file that's being used (*L/nodejs-ex (1)/.project*) is in a project that the chromium tooling created behind the scenes. It is not visible in the project explorer but it is in the navigator (decorated with a chrome tools icon):
!image-2018-07-02-22-49-45-246.png!
This latter project is created and opened by the chromium tools in
{code:title=org.eclipse.wst.jsdt.chromium.debug.core.util.ChromiumDebugPluginUtil#createEmptyProject}
try {
project.create(description, null);
project.open(null);
return project;
} catch (CoreException e) {
ChromiumDebugPlugin.log(e);
return null;
}
{code}
*project.open(null)* causes the *CheckMissingNaturesListener* to check for the missing natures.
{code}
CheckMissingNaturesListener$3(InternalWorkspaceJob).<init>(String) line: 27
CheckMissingNaturesListener$3(WorkspaceJob).<init>(String) line: 63
CheckMissingNaturesListener$3.<init>(CheckMissingNaturesListener, String, Set, IProject, Set) line: 163
CheckMissingNaturesListener.updateMarkers(Collection<IProject>) line: 163
CheckMissingNaturesListener.resourceChanged(IResourceChangeEvent) line: 46
NotificationManager$1.run() line: 297
SafeRunner.run(ISafeRunnable) line: 42
NotificationManager.notify(ResourceChangeListenerList$ListenerEntry[], ResourceChangeEvent, boolean) line: 287
NotificationManager.broadcastChanges(ElementTree, ResourceChangeEvent, boolean) line: 150
Workspace.broadcastPostChange() line: 376
Workspace.endOperation(ISchedulingRule, boolean) line: 1499
Project.open(int, IProgressMonitor) line: 1098
Project.open(IProgressMonitor) line: 1107
ChromiumDebugPluginUtil.createEmptyProject(String) line: 143
VProjectWorkspaceBridge.<init>(String, ConnectedTargetData, JavascriptVm) line: 101
VProjectWorkspaceBridge$FactoryImpl.attachedToVm(ConnectedTargetData, JavascriptVm) line: 78
ConnectedTargetData.initWorkspaceRelations() line: 222
ConnectedTargetData.setVmEmbedder(JavascriptVmEmbedder) line: 85
DebugTargetImpl.attach(DebugTargetImpl, JavascriptVmEmbedder$ConnectionToRemote, DestructingGuard, Runnable, IProgressMonitor) line: 86
StandaloneV8LaunchType(LaunchTypeBase).launch(ILaunchConfiguration, String, ILaunch, IProgressMonitor) line: 101
LaunchConfigurationWorkingCopy(LaunchConfiguration).launch(String, IProgressMonitor, boolean, boolean) line: 859
LaunchConfigurationWorkingCopy(LaunchConfiguration).launch(String, IProgressMonitor, boolean) line: 717
DebugUIPlugin.buildAndLaunch(ILaunchConfiguration, String, IProgressMonitor) line: 1039
DebugUIPlugin$8.run(IProgressMonitor) line: 1256
Worker.run() line: 60
{code}
> Server adapter: NPE when starting adapter into Debug
> -----------------------------------------------------
>
> Key: JBIDE-26158
> URL: https://issues.jboss.org/browse/JBIDE-26158
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: upstream
> Fix For: 4.10.0.AM1
>
> Attachments: image-2018-07-02-22-33-13-396.png, image-2018-07-02-22-49-45-246.png, image-2018-07-02-23-17-34-099.png, image-2018-07-03-00-03-56-346.png, screenshot-1.png, screenshot-2.png
>
>
> steps:
> # EXEC: launch new application wizard, choose nodejs-mongo-persistent template and finish
> # EXEC: when asked import the app and create a server adapter
> # ASSERT: server adapter is created
> # EXEC: start the server adapter
> # ASSERT: server adapter is launched
> # EXEC: restart the server adapter into Debug
> Result:
> Debuggin works, but you get the following error dialog:
> !image-2018-07-02-22-33-13-396.png!
> In the Eclipse log you'll find the following:
> {code}
> java.lang.NullPointerException
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener.updateRange(CheckMissingNaturesListener.java:209)
> at org.eclipse.core.internal.resources.CheckMissingNaturesListener$3.runInWorkspace(CheckMissingNaturesListener.java:179)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> ps. project context menu: Convert > Javascript Project doesn't help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4735) Central projects Wizard sometimes fails to open
by Vojtech Prusa (Jira)
Vojtech Prusa created JBDS-4735:
-----------------------------------
Summary: Central projects Wizard sometimes fails to open
Key: JBDS-4735
URL: https://issues.jboss.org/browse/JBDS-4735
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: central
Affects Versions: 12.9.0.GA
Environment: manually Fedora 28
Reporter: Vojtech Prusa
Attachments: central.tar.gz, image-2018-10-17-09-24-31-555.png
Sometimes central examples wizards fail to load and modal dialog is shown instead (screen attached).
Nothing in Error log view.
Restarting devstudio solves the issue.
Adding screen and central tar of:
devstudio-12.9.0.GA-v20180928-1629-B3448/workspaces/workspace/.metadata/.plugins/org.jboss.tools.central/central
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26389) NPE while "Searching Runtimes"
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26389?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-26389.
---------------------------------
Verified on 12.9.0.AM1-v20181016-1931-B3528.
> NPE while "Searching Runtimes"
> ------------------------------
>
> Key: JBIDE-26389
> URL: https://issues.jboss.org/browse/JBIDE-26389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.9.0.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.10.0.AM1
>
>
> {code}
> eclipse.buildId=12.9.0.GA-v20180928-1629-B3448
> java.version=1.8.0_181
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/odockal/workspace1290GA/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Sun Sep 30 20:56:59 CEST 2018
> An internal error occurred during: "Searching runtimes...".
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderWhiteListBin(UnifiedMinishiftRuntimeDetector.java:150)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.getMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:139)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.folderContainsMinishiftBinary(UnifiedMinishiftRuntimeDetector.java:144)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.minishiftHomeMatches(UnifiedMinishiftRuntimeDetector.java:180)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.UnifiedMinishiftRuntimeDetector.matches(UnifiedMinishiftRuntimeDetector.java:171)
> at org.jboss.tools.openshift.internal.cdk.server.core.detection.AbstractCDKRuntimeDetector.exists(AbstractCDKRuntimeDetector.java:111)
> at org.jboss.tools.runtime.core.internal.RuntimeDetector.exists(RuntimeDetector.java:68)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:131)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:122)
> at org.jboss.tools.runtime.core.util.RuntimeModelUtil.verifyRuntimeDefinitionCreated(RuntimeModelUtil.java:118)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.wouldOpenSearchRuntimePathDialog(RuntimeScanner.java:152)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner.access$0(RuntimeScanner.java:129)
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:81)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26407) Server adapter: fails with a NPE if there's no oc configured
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26407:
---------------------------------------
[~adietish] No problem, I just need to wait for subscription renewal, I've just found out that it got expired a couple of days ago.
> Server adapter: fails with a NPE if there's no oc configured
> -------------------------------------------------------------
>
> Key: JBIDE-26407
> URL: https://issues.jboss.org/browse/JBIDE-26407
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: oc_binary, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: start with a workspace where's no preference that points to an oc binary
> # ASSERT: have the connection *NOT* overriding the oc binary location
> # EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template), have the project imported to your workspace and the server adapter created
> # EXEC: start the server adapter
> Result:
> you get an error dialog reporting an NPE
> !screenshot-1.png!
> The following can be spotted in the Eclipse log:
> {code}
> java.lang.NullPointerException
> at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022)
> at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017)
> at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:36)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26407) Server adapter: fails with a NPE if there's no oc configured
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26407 at 10/16/18 11:21 AM:
---------------------------------------------------------------------
I cannot reproduce this error. What I get is the tooling reporting correctly that no oc could be found:
!screenshot-2.png!
[~jkopriva], [~odockal]: can I ask you to please try to reproduce this?
was (Author: adietish):
I cannot reproduce this error. What I get is the tooling reporting correctly that no oc could be found:
!screenshot-2.png!
[~jkopriva] [~odockal] can I ask you to please try to reproduce this?
> Server adapter: fails with a NPE if there's no oc configured
> -------------------------------------------------------------
>
> Key: JBIDE-26407
> URL: https://issues.jboss.org/browse/JBIDE-26407
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: oc_binary, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: start with a workspace where's no preference that points to an oc binary
> # ASSERT: have the connection *NOT* overriding the oc binary location
> # EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template), have the project imported to your workspace and the server adapter created
> # EXEC: start the server adapter
> Result:
> you get an error dialog reporting an NPE
> !screenshot-1.png!
> The following can be spotted in the Eclipse log:
> {code}
> java.lang.NullPointerException
> at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022)
> at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017)
> at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:36)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26407) Server adapter: fails with a NPE if there's no oc configured
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26407:
------------------------------------------
I cannot reproduce this error. What I get is the tooling reporting correctly that no oc could be found:
!screenshot-2.png!
> Server adapter: fails with a NPE if there's no oc configured
> -------------------------------------------------------------
>
> Key: JBIDE-26407
> URL: https://issues.jboss.org/browse/JBIDE-26407
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: oc_binary, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> steps:
> # ASSERT: start with a workspace where's no preference that points to an oc binary
> # ASSERT: have the connection *NOT* overriding the oc binary location
> # EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template), have the project imported to your workspace and the server adapter created
> # EXEC: start the server adapter
> Result:
> you get an error dialog reporting an NPE
> !screenshot-1.png!
> The following can be spotted in the Eclipse log:
> {code}
> java.lang.NullPointerException
> at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022)
> at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017)
> at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51)
> at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:36)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months