[JBoss JIRA] (JBDS-4571) SWTException prevents Getting Started tab from populating
by Leo Ufimtsev (JIRA)
[ https://issues.jboss.org/browse/JBDS-4571?page=com.atlassian.jira.plugin.... ]
Leo Ufimtsev commented on JBDS-4571:
------------------------------------
I fixed the issue upstream and verified that Red Hat Central works on it (See attached screenshot). Tomorrows/Monday's SWT build should contain fix.
> SWTException prevents Getting Started tab from populating
> ---------------------------------------------------------
>
> Key: JBDS-4571
> URL: https://issues.jboss.org/browse/JBDS-4571
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update, upstream
> Affects Versions: 11.0.0.GA
> Environment: Fedora 26 x86_64
> webkitgtk4-2.16.6-1.fc26.x86_64
> devstudio-11.0.0.GA-installer-standalone.jar
> openjdk version "1.8.0_144"
> OpenJDK Runtime Environment (build 1.8.0_144-b01)
> OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)
> Reporter: Roland Grunberg
> Assignee: Nick Boldt
> Fix For: 11.x
>
>
> # Using the Devstudio installer ($ java -jar /notnfs/Downloads/devstudio-11.0.0.GA-installer-standalone.jar), I installed in '/notnfs/devstudio' (not in a home folder), with the default system JVM.
> # On startup (can be from the install, or separately), create a workspace in $HOME/workspace-devstudio.
> # Red Hat Central view loads, with the 'Do Not Enter' icon and the text 'An exception was raised in Javascript'. Clicking on the 'Details >>' button shows the full stacktrace, and it is not logged into the Error Log view.
> Note that switching to the Software/Update tab gets the Red Hat Central view to become populated with the correct content so the issue seems isolated to the 'Getting Started' tab.
> https://paste.fedoraproject.org/paste/Y5jrMNBt86LoEAsqIGykTg
> The relevant part seems to be :
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25098) Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25098?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-25098:
-----------------------------------
Assignee: Aurélien Pupier
Resolution: Done
> Provide a status preserving the stacktrace in DownloadRuntimeOperationUtility.downloadAndUnzip
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-25098
> URL: https://issues.jboss.org/browse/JBIDE-25098
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Fix For: 4.5.1.AM3
>
>
> in org.jboss.tools.runtime.core.util.internal.DownloadRuntimeOperationUtility.downloadAndUnzip(String, String, String, boolean, String, String, TaskModel, IProgressMonitor)
> a status is directly returned instead of following the guidelines explained in the javadoc for CoreException.getStatus to recreate a Status which will preserve the stacktrace
> {noformat}
> IStatus org.eclipse.core.runtime.CoreException.getStatus()
> Returns the status object for this exception.
> IMPORTANT:
> The result must NOT be used for logging, error reporting, or as a method return value, since that code pattern hides the original stack trace. Instead, create a new Status with your plug-in ID and this CoreException, and use that new status for error reporting or as a method return value. For example, instead of:
> yourPlugin.getLog().log(exception.getStatus());
>
> Use: IStatus result = new Status(exception.getStatus().getSeverity(), pluginId, message, exception);
> yourPlugin.getLog().log(result);
>
> Returns:a status object
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25060) Make CDK integration tests run on mac machines in jenkins
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25060?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25060:
----------------------------------
Description:
Prepare job be be able to run cdk on macOS based slaves.
Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps:
# Download proper version of docker-machine-driver-xhyve binary
# enabled root access to this binary and add it into wheel group
# Add user as owner of the file
Execute on these machines:
* bigmek
* domek
* zamek
Refrence: https://docs.openshift.org/latest/minishift/getting-started/setting-up-dr...
was:
Prepare job be be able to run cdk on macOS based slaves.
Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps:
# Download proper version of docker-machine-driver-xhyve binary
# enabled access to this binary
# Add user as owner of the file
Execute on these machines:
* bigmek
* domek
* zamek
> Make CDK integration tests run on mac machines in jenkins
> ---------------------------------------------------------
>
> Key: JBIDE-25060
> URL: https://issues.jboss.org/browse/JBIDE-25060
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: central-ci, jenkins
> Fix For: 4.5.1.AM3
>
>
> Prepare job be be able to run cdk on macOS based slaves.
> Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps:
> # Download proper version of docker-machine-driver-xhyve binary
> # enabled root access to this binary and add it into wheel group
> # Add user as owner of the file
> Execute on these machines:
> * bigmek
> * domek
> * zamek
> Refrence: https://docs.openshift.org/latest/minishift/getting-started/setting-up-dr...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25060) Make CDK integration tests run on mac machines in jenkins
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25060?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25060:
----------------------------------
Description:
Prepare job be be able to run cdk on macOS based slaves.
Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps:
# Download proper version of docker-machine-driver-xhyve binary
# enabled access to this binary
# Add user as owner of the file
Execute on these machines:
* bigmek
* domek
* zamek
was:Prepare job be be able to run cdk on macOS based slaves.
> Make CDK integration tests run on mac machines in jenkins
> ---------------------------------------------------------
>
> Key: JBIDE-25060
> URL: https://issues.jboss.org/browse/JBIDE-25060
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: central-ci, jenkins
> Fix For: 4.5.1.AM3
>
>
> Prepare job be be able to run cdk on macOS based slaves.
> Upgrade macOS based slaves to utilize xhyve for cdk. This would requires to configure those steps:
> # Download proper version of docker-machine-driver-xhyve binary
> # enabled access to this binary
> # Add user as owner of the file
> Execute on these machines:
> * bigmek
> * domek
> * zamek
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25051) Deadlock after startup
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25051?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov closed JBIDE-25051.
------------------------------------
Resolution: Rejected
> Deadlock after startup
> ----------------------
>
> Key: JBIDE-25051
> URL: https://issues.jboss.org/browse/JBIDE-25051
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Emond Papegaaij
> Priority: Minor
> Attachments: Screenshot_20170926_103927.png, eclipse-stackdump.txt
>
>
> Eclipse deadlocked on me directly after startup (the workspace is shown). As the deadlock involves main, the UI is frozen entirely. I've reported the bug to Eclipse IDE first, but they suggested it is likely a JBoss Tools bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months