[JBoss JIRA] (JBDS-3603) NoStackTrace below DiscoveryViewer$18.run
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3603?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3603:
---------------------------------
Component/s: central-update
(was: aeri)
> NoStackTrace below DiscoveryViewer$18.run
> -----------------------------------------
>
> Key: JBDS-3603
> URL: https://issues.jboss.org/browse/JBDS-3603
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.CR1
> Reporter: Automated Error Reporting Bot
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3603) NoStackTrace below DiscoveryViewer$18.run
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3603?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3603:
------------------------------------
Assignee: Nick Boldt
cc: [~mickael_istria]
> NoStackTrace below DiscoveryViewer$18.run
> -----------------------------------------
>
> Key: JBDS-3603
> URL: https://issues.jboss.org/browse/JBDS-3603
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.CR1
> Reporter: Automated Error Reporting Bot
> Assignee: Nick Boldt
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3958?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3958:
------------------------------
Fix Version/s: 10.0.1.AM2
> Transpile code at build time instead of run time
> ------------------------------------------------
>
> Key: JBDS-3958
> URL: https://issues.jboss.org/browse/JBDS-3958
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Jan Richter
> Fix For: 10.0.1.AM2
>
>
> The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
> Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-3769:
---------------------------------
Assignee: Jan Richter
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.1.AM2
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3651:
-----------------------------------
The main subtasks are tracked in the following issues:
* Remove JSPM from dependencies: JBDS-3769
* Transpile code at build time instead of run time: JBDS-3958
After these tasks are done, hopefully the initial load time will be improved drastically.
> Reduce the delay between the main window opening and the first page being rendered
> ----------------------------------------------------------------------------------
>
> Key: JBDS-3651
> URL: https://issues.jboss.org/browse/JBDS-3651
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
>
> Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up.
> I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously.
> We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3958?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3958:
------------------------------
Description:
The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
was:
The major slowing factor in the initial load time is babel transpiling the code at when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
> Transpile code at build time instead of run time
> ------------------------------------------------
>
> Key: JBDS-3958
> URL: https://issues.jboss.org/browse/JBDS-3958
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Jan Richter
>
> The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
> Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
Jan Richter created JBDS-3958:
---------------------------------
Summary: Transpile code at build time instead of run time
Key: JBDS-3958
URL: https://issues.jboss.org/browse/JBDS-3958
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Affects Versions: 10.0.0.GA
Reporter: Jan Richter
Assignee: Jan Richter
The major slowing factor in the initial load time is babel transpiling the code at when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3769:
------------------------------
Fix Version/s: 10.0.1.AM2
(was: 10.0.1.AM1)
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.1.AM2
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3651:
------------------------------
Fix Version/s: 10.0.1.AM2
(was: 10.0.1.AM1)
> Reduce the delay between the main window opening and the first page being rendered
> ----------------------------------------------------------------------------------
>
> Key: JBDS-3651
> URL: https://issues.jboss.org/browse/JBDS-3651
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
>
> Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up.
> I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously.
> We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months