[JBoss JIRA] (ERT-536) [Gtk3][Webkit2] Port clearSessions(), getCookie() and setCookie() to webkit2. [EBZ#522181]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-536:
---------------------------------------
Summary: [Gtk3][Webkit2] Port clearSessions(), getCookie() and setCookie() to webkit2. [EBZ#522181]
Key: ERT-536
URL: https://issues.jboss.org/browse/ERT-536
Project: Eclipse Release Train
Issue Type: Task
Components: Platform
Reporter: Friendly Jira Robot
Created attachment 270164
hs_err_pid20835.log
Build ID: 20170907-1650_eclipse-cpp-oxygen-1-RC3-linux.gtk.x86_64.tar.gz
Host: Ubuntu 16.04.2 on Virtualbox 5.1.26, 3D acceleration + guest utilities on
GTK: libwebkit2gtk-4.0-37:amd64 2.16.6-0ubuntu0.16.04.1
Eclipse crashed hard on me with attached hs_err_pid20835.log , here are the top frames from the stack:
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.eclipse.swt.internal.webkit.WebKitGTK._webkit_get_default_session()J+0
j org.eclipse.swt.internal.webkit.WebKitGTK.webkit_get_default_session()J+7
j org.eclipse.swt.browser.WebKit.lambda$0()V+7
j org.eclipse.swt.browser.WebKit$$Lambda$328.run()V+0
j org.eclipse.swt.browser.WebBrowser.clearSessions()V+9
j org.eclipse.swt.browser.Browser.clearSessions()V+0
j org.eclipse.oomph.ui.HelpSupport.setHelpPath(Ljava/lang/String;)V+31
j org.eclipse.oomph.ui.HelpSupport.updateHelp()V+11
The issue is not reproducible, but here's the steps I had performed:
1. Launch Eclipse, close the welcome screen (Note: Welcome screen is empty)
2. Import a C/C++ project, allow it to be fully indexed
3. Launch a GDB debug session
4. Window > Preferences, enable the Oomph Preference Recorder
5. Preferences:Filter:GDB, Enable "GDB Traces", click "Apply and Close"
--> The Oomph confirmation dialog briefly appeared
--> Then an Ubuntu dialog said "WebKitNetworkProcess died" and Eclipse was gone
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25263:
-------------------------------
Sprint: (was: devex #142 December 2017)
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Assignee: Jeff MAURY
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25263) OSIO Error refreshing token
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25263?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25263:
-------------------------------
Sprint: devex #142 December 2017
> OSIO Error refreshing token
> ---------------------------
>
> Key: JBIDE-25263
> URL: https://issues.jboss.org/browse/JBIDE-25263
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Lucia Jelinkova
> Assignee: Jeff MAURY
> Labels: OSIO
> Fix For: 4.5.x
>
>
> When I called the OSIO service from Fabric8 plugin, the following error occurred.
> {code:java}
> org.jboss.tools.openshift.io.core.exception.OpenshiftIORefreshException: Error refreshing token for ljelinko(a)redhat.com on cluster OpenShift.io
> at org.jboss.tools.openshift.io.core.AccountService.performRefresh(AccountService.java:168)
> at org.jboss.tools.openshift.io.core.AccountService.getToken(AccountService.java:101)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:24)
> at org.jboss.tools.openshift.io.internal.core.DefaultTokenProvider.apply(DefaultTokenProvider.java:1)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.TokenCheck.getToken(TokenCheck.java:60)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.checkPreferences(Fabric8AnalyticsStreamConnectionProvider.java:67)
> at com.redhat.fabric8analytics.lsp.eclipse.ui.Fabric8AnalyticsStreamConnectionProvider.<init>(Fabric8AnalyticsStreamConnectionProvider.java:54)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.lsp4e.LanguageServersRegistry$ExtensionLanguageServerDefinition.createConnectionProvider(LanguageServersRegistry.java:102)
> at org.eclipse.lsp4e.ProjectSpecificLanguageServerWrapper.<init>(ProjectSpecificLanguageServerWrapper.java:142)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrapperForConnection(LanguageServiceAccessor.java:199)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSWrappers(LanguageServiceAccessor.java:163)
> at org.eclipse.lsp4e.LanguageServiceAccessor.getLSPDocumentInfosFor(LanguageServiceAccessor.java:261)
> at org.eclipse.lsp4e.ConnectDocumentToLanguageServerSetupParticipant$1.run(ConnectDocumentToLanguageServerSetupParticipant.java:74)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> Well, I can see from the code that there was some unexpected response from OSIO server but it would be helpful if you could provide some more information, at least the server's true response code. In this case the user is absolutely clueless as what happend.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (ERT-534) support building with Tycho 1.0 [EBZ#526333]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-534?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-534:
---------------------------
Sprint: devex #141 December 2017
> support building with Tycho 1.0 [EBZ#526333]
> --------------------------------------------
>
> Key: ERT-534
> URL: https://issues.jboss.org/browse/ERT-534
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Webservices
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Labels: 3.10_M4, bzira, jst.ws
> Fix For: Photon (4.8) M4
>
>
> Quick hack to support Tycho 1.0 (instead of <= 0.26.0) is to enable tycho-compiler-plugin's useProjectSettings=false [1] so that things like API restrictions that SHOULD fail the build are allowed.
> Ultimately, these API violation should be fixed, but if your Eclipse settings are allowing these to be ignored as warnings instead of errors, then so too should Tycho do the same.
> Thus we need to add this to the root pom:
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-compiler-plugin</artifactId>
> <version>${tycho.version}</version>
> <configuration>
> <useProjectSettings>false</useProjectSettings>
> </configuration>
> </plugin>
> </plugins>
> </build>
> [1] https://wiki.eclipse.org/Tycho/Release_Notes/1.0.0#Compiler
> BTW, the Version here should be 3.10, but bugzilla needs to be updated to add that fixversion.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (ERT-531) Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/ERT-531?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt updated ERT-531:
---------------------------
Sprint: devex #141 December 2017
> Maven 3.3.1 doesn't pick up the customized Toolchain for the WTP build [EBZ#472084]
> -----------------------------------------------------------------------------------
>
> Key: ERT-531
> URL: https://issues.jboss.org/browse/ERT-531
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Community
> Reporter: Friendly Jira Robot
> Assignee: Nick Boldt
> Priority: Critical
> Labels: Hudson, bzira
>
> A few WTP plugins need to build with the old JDK and a WTP toolchains.xml is set up. It works fine with Maven 3.2.5 but fails with Maven 3.3.1.
> The current investigation showed that instead of using the WTP specific toolchains.xml which is defined in the Hudson build configuration, a common toolchains /opt/public/common/maven-toolchains.xml is linked as the user toolchains.
> genie.gef ~> ll ~/.m2
> [....]
> lrwxrwxrwx 1 genie.gef tools.gef 37 23 févr. 04:05 settings.xml -> /opt/public/common/maven-settings.xml
> lrwxrwxrwx 1 genie.gef tools.gef 39 23 févr. 04:05 toolchains.xml -> /opt/public/common/maven-toolchains.xml
> I wonder how Maven 3.2.5 can pick up the customized toolchains but not 3.3.1. It would be great if Maven 3.3.1 can pick up the customized toolchains as 3.2.5.
> At the same time, I wonder whether the common toolchains file can be changed to support IBM JDK 1.4. Its current JDK 1.4 points to the Sun's which is broken and generates compile errors.
> <toolchain>
> <type>jdk</type>
> <provides>
> <id>J2SE-1.4</id>
> </provides>
> <configuration>
> <jdkHome>/shared/webtools/apps/IBMJava2-142-SR13FP10/jre</jdkHome>
> </configuration>
> </toolchain>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months