GWT symbol maps are now installed with Engine, the "debuginfo" packages are out
Hello everyone, in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade. There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove them manually before upgrading Engine.) Please refer to commit msg for details. [1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/ Regards, Vojtech
Hi! When building the Engine manually, is it possible to get de-obfuscated stack traces without rebuilding with DEV_BUILD_GWT_DRAFT=1 ? Shmuel On Thu, Jun 8, 2017 at 8:17 PM, Vojtech Szocs <vszocs@redhat.com> wrote:
Hello everyone,
in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade.
There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove them manually before upgrading Engine.)
Please refer to commit msg for details.
[1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/
Regards, Vojtech
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Yes, they'll now be in ui.log on the server. Greg On Thu, Jun 8, 2017 at 1:32 PM, Shmuel Melamud <smelamud@redhat.com> wrote:
Hi!
When building the Engine manually, is it possible to get de-obfuscated stack traces without rebuilding with DEV_BUILD_GWT_DRAFT=1 ?
Shmuel
Hello everyone,
in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade.
There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove
On Thu, Jun 8, 2017 at 8:17 PM, Vojtech Szocs <vszocs@redhat.com> wrote: them
manually before upgrading Engine.)
Please refer to commit msg for details.
[1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/
Regards, Vojtech
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
On Thu, Jun 8, 2017 at 7:37 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Yes, they'll now be in ui.log on the server.
Greg
On Thu, Jun 8, 2017 at 1:32 PM, Shmuel Melamud <smelamud@redhat.com> wrote:
Hi!
When building the Engine manually, is it possible to get de-obfuscated stack traces without rebuilding with DEV_BUILD_GWT_DRAFT=1 ?
Shmuel
Hello everyone,
in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade.
There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove
On Thu, Jun 8, 2017 at 8:17 PM, Vojtech Szocs <vszocs@redhat.com> wrote: them
manually before upgrading Engine.)
This is bad, we should not require manual uninstallation during upgrades. Could you please add correct Provides/Conflicts into webadmin/userportal packages, so existing debuginfo packages will be uninstalled automatically?
Please refer to commit msg for details.
[1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/
Regards, Vojtech
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
On Thu, Jun 8, 2017 at 3:50 PM, Martin Perina <mperina@redhat.com> wrote:
On Thu, Jun 8, 2017 at 7:37 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Yes, they'll now be in ui.log on the server.
Greg
On Thu, Jun 8, 2017 at 1:32 PM, Shmuel Melamud <smelamud@redhat.com> wrote:
Hi!
When building the Engine manually, is it possible to get de-obfuscated stack traces without rebuilding with DEV_BUILD_GWT_DRAFT=1 ?
Shmuel
Hello everyone,
in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade.
There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove
On Thu, Jun 8, 2017 at 8:17 PM, Vojtech Szocs <vszocs@redhat.com> wrote: them
manually before upgrading Engine.)
This is bad, we should not require manual uninstallation during upgrades. Could you please add
correct Provides/Conflicts into webadmin/userportal packages, so existing debuginfo packages will be uninstalled automatically?
Normally it is probably bad. We discussed this in the patch comments. Quoting Sandro [3]: """ about yum update error messages related to version locking: debug packages are not meant to be installed on any production environment other than for debugging purpose. Once the debug is finished they need to be removed. """ See the patch [1] for more of the conversation. [3] https://bugzilla.redhat.com/show_bug.cgi?id=1401963#c23 Greg
Please refer to commit msg for details.
[1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/
Regards, Vojtech
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
On Thu, Jun 8, 2017 at 11:16 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
On Thu, Jun 8, 2017 at 3:50 PM, Martin Perina <mperina@redhat.com> wrote:
On Thu, Jun 8, 2017 at 7:37 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Yes, they'll now be in ui.log on the server.
Greg
On Thu, Jun 8, 2017 at 1:32 PM, Shmuel Melamud <smelamud@redhat.com> wrote:
Hi!
When building the Engine manually, is it possible to get de-obfuscated stack traces without rebuilding with DEV_BUILD_GWT_DRAFT=1 ?
Shmuel
Hello everyone,
in master [1] and 4.1 [2] branches, meaningful (de-obfuscated) GWT/Java stack traces are now available right after Engine installation or upgrade.
There's no need to install the complementary "debuginfo" packages anymore. In fact, those packages are removed now. (If installed, please remove
On Thu, Jun 8, 2017 at 8:17 PM, Vojtech Szocs <vszocs@redhat.com> wrote: them
manually before upgrading Engine.)
This is bad, we should not require manual uninstallation during upgrades. Could you please add
correct Provides/Conflicts into webadmin/userportal packages, so existing debuginfo packages will be uninstalled automatically?
Normally it is probably bad. We discussed this in the patch comments. Quoting Sandro [3]:
""" about yum update error messages related to version locking: debug packages are not meant to be installed on any production environment other than for debugging purpose. Once the debug is finished they need to be removed. """
Right, those "debuginfo" packages are complementary and expected to be removed once no longer needed (e.g. after collecting GWT/Java stack trace information when reporting a UI related bug). As Greg wrote, this was discussed in patch [1], please see the review comments from Simone, Sandro and Didi.
See the patch [1] for more of the conversation.
[3] https://bugzilla.redhat.com/show_bug.cgi?id=1401963#c23
Greg
Please refer to commit msg for details.
[1] https://gerrit.ovirt.org/#/c/75420 [2] https://gerrit.ovirt.org/#/c/77892/
Regards, Vojtech
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Greg Sheremeta, MBA Sr. Software Engineer Red Hat, Inc. gshereme@redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (4)
-
Greg Sheremeta -
Martin Perina -
Shmuel Melamud -
Vojtech Szocs