ice issueshttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues2020-11-12T20:36:55Zhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/492Set @DataField's nullable to true by default2020-11-12T20:36:55ZEclipse WebmasterSet @DataField's nullable to true by default*Created by: dbluhm*
Suggestion from @walshmm: in practice, it seems that having the `nullable` property set to `true` by default is more desirable than our current default of `false`.
Having it set as false will cause the Lombok `@N...*Created by: dbluhm*
Suggestion from @walshmm: in practice, it seems that having the `nullable` property set to `true` by default is more desirable than our current default of `false`.
Having it set as false will cause the Lombok `@NonNull` annotation to be applied to the field's type, triggering an exception if there's any attempt to set the value to null.https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/355Introduce a sample Vaadin bundle and resolve build issues.2019-08-28T14:32:40ZEclipse WebmasterIntroduce a sample Vaadin bundle and resolve build issues.*Created by: knram06*
The aim is
1. To introduce a Vaadin bundle that demonstrates how to connect to a Core instance using OSGi, into the repository.
2. Ensure that the relevant project build properties are updated and ICE builds co...*Created by: knram06*
The aim is
1. To introduce a Vaadin bundle that demonstrates how to connect to a Core instance using OSGi, into the repository.
2. Ensure that the relevant project build properties are updated and ICE builds correctly.
The sample Vaadin app is based on Jay's work in prototyping a Vaadin application to use OSGi services as outlined in:
http://www.jayjaybillings.com/thesis/eclipse/2016/12/14/vaadin-and-osgi.html
This request is from Ram from RNET to support efforts to prototype a web-based interface using ICE.Alex McCaskeyAlex McCaskeyhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/354Create a Product Configuration for the headless Core instance.2017-03-30T20:01:05ZEclipse WebmasterCreate a Product Configuration for the headless Core instance.*Created by: knram06*
The aim is to create a product configuration for a headless Core instance.
1. To allow the launch of Core in a manner similar to the Core OSGi.launch file, but without having to go through ICE.
2. To have a sta...*Created by: knram06*
The aim is to create a product configuration for a headless Core instance.
1. To allow the launch of Core in a manner similar to the Core OSGi.launch file, but without having to go through ICE.
2. To have a standalone package or JAR that can be executed on a system to bring up a Core instance.
3. This is to let a Client instance/frontend to connect to this Core.
This is being requested by Ram from RNET as part of an effort to prototype a web-based interface using ICE.https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/314VIBE Model needs error messages when importing2016-12-13T16:10:42ZEclipse WebmasterVIBE Model needs error messages when importing*Created by: SmithRWORNL*
The VIBE Model should display an error message when there are problems loading, instead of only logging the error without alerting the user.*Created by: SmithRWORNL*
The VIBE Model should display an error message when there are problems loading, instead of only logging the error without alerting the user.https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/312VIBE Items are not imported correctly2017-01-03T18:17:06ZEclipse WebmasterVIBE Items are not imported correctly*Created by: SmithRWORNL*
Importing a VIBE Item will often fail, falling back to the default values, due to problems with the way the IPSReader handles commented lines and a lack of support for some port types.*Created by: SmithRWORNL*
Importing a VIBE Item will often fail, falling back to the default values, due to problems with the way the IPSReader handles commented lines and a lack of support for some port types.https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/295Host table is requiring connection information to be reentered2019-08-28T14:34:07ZEclipse WebmasterHost table is requiring connection information to be reentered*Created by: SmithRWORNL*
Entering an unrecognized connection name in the hosts table in an Item, then configuring the connection so that it fails, may result in the table forcing the user to re-input all the information for the connect...*Created by: SmithRWORNL*
Entering an unrecognized connection name in the hosts table in an Item, then configuring the connection so that it fails, may result in the table forcing the user to re-input all the information for the connection every time the Item is processed, even after it has already been replaced by a valid connection in the table.VIBE 2.0 Releasehttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/294VIBE launcher needs input file error checking2016-11-29T16:19:46ZEclipse WebmasterVIBE launcher needs input file error checking*Created by: SmithRWORNL*
Currently, when an invalid file is specified and the job launched in VIBE, the form gets stuck in the "Processing Form..." stage. Instead, the launcher should detect when an invalid file has been supplied and r...*Created by: SmithRWORNL*
Currently, when an invalid file is specified and the job launched in VIBE, the form gets stuck in the "Processing Form..." stage. Instead, the launcher should detect when an invalid file has been supplied and return an error message.VIBE 2.0 Releasehttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/290Re-add hosts table file for JobLaunchers2019-08-28T14:34:06ZEclipse WebmasterRe-add hosts table file for JobLaunchers*Created by: jayjaybillings*
We need to have the ability to change the default hosts in a JobLauncher at deployment time in addition to build time and run time.
Once upon a time we had this ability, but I dumped it years back. The si...*Created by: jayjaybillings*
We need to have the ability to change the default hosts in a JobLauncher at deployment time in addition to build time and run time.
Once upon a time we had this ability, but I dumped it years back. The simplest way to do this is to provide a file that lists the extra hosts and to read that file on startup. In the past this depended on on a hardwired path in the workspace, but I will configure this so that the user can provide a path in the ICE INI file instead.2.2.1https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/287Need to add a tutorial on doing an installation to the host version of ICE2019-08-28T14:34:06ZEclipse WebmasterNeed to add a tutorial on doing an installation to the host version of ICE*Created by: jayjaybillings*
I'm at SC16 and trying to add a SuiteLauncher for the KokkosTutorial to ICE. Everything has worked so far, in part because I am exporting my plugins to the host version of ICE where I wrote them. Tutorials o...*Created by: jayjaybillings*
I'm at SC16 and trying to add a SuiteLauncher for the KokkosTutorial to ICE. Everything has worked so far, in part because I am exporting my plugins to the host version of ICE where I wrote them. Tutorials on that process are available at
http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Fguide%2Ftools%2Fexport_wizards%2Fexport_plugins.htm
and
http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.pde.doc.user%2Ftasks%2Fui_export_install_into_host.htm
We need to work this into our tutorials because it is far, far easier to do this than rebuilding ICE from scratch. I didn't even need to check out the code for ICE into my workspace. Instead, I have just used the version of ICE installed to create my plugins, exported them to the local installation, and then updated as needed. Thus we could rewrite our entire tutorial stack to have an entirely different structure that is much easier.2.2.1https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/286Need a SuiteLauncher tutorial2019-08-28T14:34:05ZEclipse WebmasterNeed a SuiteLauncher tutorial*Created by: jayjaybillings*
I'm trying to create a SuiteLauncher without looking at its source code and finding it difficult. Thus I think we need to build a tutorial for it.*Created by: jayjaybillings*
I'm trying to create a SuiteLauncher without looking at its source code and finding it difficult. Thus I think we need to build a tutorial for it.2.2.1https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/285Javadoc is hard to find2020-10-29T15:27:41ZEclipse WebmasterJavadoc is hard to find*Created by: jayjaybillings*
Finding the Javadoc needs to be easier. It is currently buried far down the documentation page. It should be placed:
* Higher on the wiki, possibly on the main page.
* On the home page.
We may want to c...*Created by: jayjaybillings*
Finding the Javadoc needs to be easier. It is currently buried far down the documentation page. It should be placed:
* Higher on the wiki, possibly on the main page.
* On the home page.
We may want to consider moving the Javadoc off of eclipseice.ornl.gov and into the Eclipse web space.2.2.1https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/278Saved JobProfileEditor fails to load2016-11-08T12:59:09ZEclipse WebmasterSaved JobProfileEditor fails to load*Created by: jayjaybillings*
Wei (Mark) Jin reported the following:
Here I came across a new problem on Job Profile Editor :
I created a new Job Profile using dir.exe on Windows 7 X64, then restarted ICE, click new Item, found new job...*Created by: jayjaybillings*
Wei (Mark) Jin reported the following:
Here I came across a new problem on Job Profile Editor :
I created a new Job Profile using dir.exe on Windows 7 X64, then restarted ICE, click new Item, found new job profile I created, double click and a error dialog came out as "java.lang.ClassCastException: com.sun.org.apache.xerces.internal.dom.ElementNSImpl cannot be cast to org.eclipse.ice.datastructures.entry.IEntry".
Did I miss something ? Need your help, Sir : )
Many thanks again~~
Mark
below is the detail.
> java.lang.ClassCastException: com.sun.org.apache.xerces.internal.dom.ElementNSImpl cannot be cast to org.eclipse.ice.datastructures.entry.IEntry
> at org.eclipse.ice.datastructures.form.DataComponent.copy(DataComponent.java:355)
> at org.eclipse.ice.datastructures.form.DataComponent.clone(DataComponent.java:378)
> at org.eclipse.ice.datastructures.form.Form.copy(Form.java:373)
> at org.eclipse.ice.item.Item.copy(Item.java:1283)
> at org.eclipse.ice.item.jobLauncher.JobLauncher.copy(JobLauncher.java:1806)
> at org.eclipse.ice.item.jobLauncher.JobLauncher.clone(JobLauncher.java:1840)
> at org.eclipse.ice.item.SerializedItemBuilder.build(SerializedItemBuilder.java:238)
> at org.eclipse.ice.core.internal.itemmanager.ItemManager.createItem(ItemManager.java:187)
> at org.eclipse.ice.core.internal.Core.createItem(Core.java:408)
> at org.eclipse.ice.core.internal.Core.createItem(Core.java:389)
> at org.eclipse.ice.client.internal.Client.createItem(Client.java:314)
> at org.eclipse.ice.client.common.wizards.NewItemWizard.performFinish(NewItemWizard.java:132)
> at org.eclipse.ice.client.common.wizards.NewItemWizardPage$4.doubleClick(NewItemWizardPage.java:245)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:833)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:830)
> at org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1151)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1264)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ice.client.common.CreateItemHandler.execute(CreateItemHandler.java:49)
> 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(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
2.2.1Alex McCaskeyAlex McCaskeyhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/262Add support for connecting to remote cores in the client2019-08-28T14:36:43ZEclipse WebmasterAdd support for connecting to remote cores in the client*Created by: jayjaybillings*
We need to add support in the client for connecting to a remote core.
Once upon a time we had this in the "ConnectCoreAction." Perhaps we can reenable that button? I don't think we will need to use the remo...*Created by: jayjaybillings*
We need to add support in the client for connecting to a remote core.
Once upon a time we had this in the "ConnectCoreAction." Perhaps we can reenable that button? I don't think we will need to use the remote core proxy though because the OSGI remote service infrastructure should be encapsulating all of that.
Instead of only having the button and manually switching, it would be nice to actually create view that listed all of the remote cores that are connected to the client.
This is to support Ram's request in #261.
2.2https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/261Add OSGI remote service support for ICore service2016-11-22T13:48:42ZEclipse WebmasterAdd OSGI remote service support for ICore service*Created by: jayjaybillings*
Ram has requested that we add support for the ICore service to be published as a remote OSGI service. Sounds like fun, so I created a branch on it. Ram is going to look at it with us.
*Created by: jayjaybillings*
Ram has requested that we add support for the ICore service to be published as a remote OSGI service. Sounds like fun, so I created a branch on it. Ram is going to look at it with us.
2.2https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/260Need to be able dynamically populate the remote hosts in response to resource...2019-08-28T14:36:42ZEclipse WebmasterNeed to be able dynamically populate the remote hosts in response to resource manager*Created by: jayjaybillings*
OSC needs the ability to reconfigure the hosts table based on the availability of resources according to a resource manager. This could look like a reconfigure on start or through a service using the remodel...*Created by: jayjaybillings*
OSC needs the ability to reconfigure the hosts table based on the availability of resources according to a resource manager. This could look like a reconfigure on start or through a service using the remodeled JobLauncher that will include more of the PTP Parallel Application Launch Configuration.
2.2https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/255404 Not Found on eclipseice.ornl.gov2019-08-28T14:36:41ZEclipse Webmaster404 Not Found on eclipseice.ornl.gov*Created by: jayjaybillings*
The Eclipse ICE downloads page at ORNL is busted. The top few directories work fine, but the P2 site returns errors on its subfolders:
http://eclipseice.ornl.gov/downloads/ice/unstable-nightly/20160812/p2/fe...*Created by: jayjaybillings*
The Eclipse ICE downloads page at ORNL is busted. The top few directories work fine, but the P2 site returns errors on its subfolders:
http://eclipseice.ornl.gov/downloads/ice/unstable-nightly/20160812/p2/features/
2.2Alex McCaskeyAlex McCaskeyhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/249ICE Restful web service is broken2016-08-07T19:59:55ZEclipse WebmasterICE Restful web service is broken*Created by: jayjaybillings*
I'm running the 20160630 build of next and the restful webservice isn't working. @SmithRWORNL confirmed that it isn't running on his version of ICE either, so I don't know how long it has been broken.
This ...*Created by: jayjaybillings*
I'm running the 20160630 build of next and the restful webservice isn't working. @SmithRWORNL confirmed that it isn't running on his version of ICE either, so I don't know how long it has been broken.
This needs to be fixed immediately because the users are RNET are wanting to build on it.
2.2Alex McCaskeyAlex McCaskeyhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/224User can't create a new MOOSE kernel using ICE2019-08-28T14:37:46ZEclipse WebmasterUser can't create a new MOOSE kernel using ICE*Created by: jayjaybillings*
**From K.N. Ramachandran:**
Hello all,
I have just started becoming familiar with Eclipse ICE and obtained a Linux binary build using the Python install script. I am currently following the instructions at ...*Created by: jayjaybillings*
**From K.N. Ramachandran:**
Hello all,
I have just started becoming familiar with Eclipse ICE and obtained a Linux binary build using the Python install script. I am currently following the instructions at https://wiki.eclipse.org/Developing_MOOSE_Applications_with_ICE and I am having some trouble here.
I am stuck at the "Adding a Kernel" section. I am facing the following issues and I feel I followed all the preceding instructions clearly.
1) I am able to Add the Kernel and I get the header and src files. But Eclipse is not able to find the "Kernel.h" and I get an "Unresolved inclusion" there as well as other places in the file.
2) Trying to execute the Make target for the Moose App only results in "Info: Nothing to build for testMoose" where testMoose is my app name.
3) When I check the Properties for testMoose, I notice an error message under the "C/C++ Build" section which says:
Toolchain "LLVM with GCC (Linux)" is not detected.
So is the LLVM toolchain necessary? I compiled libMesh using the standard Linux GCC toolchain and I had no issues there.
Any help would be greatly appreciated here.
2.2Alex McCaskeyAlex McCaskeyhttps://gitlab.eclipse.org/eclipse/ice/ice/-/issues/223jay/january/org.eclipse.january.form.feature is missing about.html2016-07-08T14:44:58ZEclipse Webmasterjay/january/org.eclipse.january.form.feature is missing about.html*Created by: jayjaybillings*
The org.eclipse.january.form.feature bundle is missing the about.html file in the jay/january branch.
*Created by: jayjaybillings*
The org.eclipse.january.form.feature bundle is missing the about.html file in the jay/january branch.
2.2https://gitlab.eclipse.org/eclipse/ice/ice/-/issues/221Input File box cannot be removed2016-06-22T20:48:08ZEclipse WebmasterInput File box cannot be removed*Created by: jayjaybillings*
The Input File box in a Job Launcher cannot be removed. Even if it is removed, it will reappear once something is imported into one of the other boxes.
Importing will work if you pick a file of the designat...*Created by: jayjaybillings*
The Input File box in a Job Launcher cannot be removed. Even if it is removed, it will reappear once something is imported into one of the other boxes.
Importing will work if you pick a file of the designated type, but the input files box definitely reappears.
This was submitted by John Eblen at our ORNL Eclipse User Group Meeting today.
2.2Alex McCaskeyAlex McCaskey