<commit_before>---
title: OVirt Engine Debug Obfuscated UI
authors: awels
wiki_title: OVirt Engine Debug Obfuscated UI
wiki_revision_count: 19
wiki_last_updated: 2016-01-06
---

# OVirt Engine Debug Obfuscated UI

## Debug Obfuscated UI

### Owner

*   Name: [<NAME>](User:awels)
*   Email: <<EMAIL>>

### Introduction

Sometimes during the usage of the Web admin or User portal you will get a popup about an uncaught exception like this:

      Uncaught exception occurred. Please try reloading the page. Details:  [some information]

In general this message lets us know something went wrong, but is less than helpful in determining what exactly went wrong. The information provided usually includes some obfuscated code like 'c is null' or 'cannot get field O5d'. None of which is very helpful.

Why is this happening now? Recently we introduced some code that captures all exceptions that are not handled anywhere else, and displays it to the user. Before the un-handled exceptions would be written to the browser console and mostly ignored unless someone looked at the browser console. They are still written to the console, but they are also reported to the user, this has some benefits and some negatives. The benefits include the fact that the user can now report something is going wrong since they are being told. The negatives include the fact that the user sees the fact that something goes wrong and they conclude the product is bad. The developers cannot fix issues they are not aware of, so in the short term we will have more bug reports but in the long term we will have a better product due the more transparent exception reporting.

#### Debugging steps

#### 1. Getting the full stack trace from the console
<commit_msg>1. Getting the full stack trace from the console<commit_after>---
title: OVirt Engine Debug Obfuscated UI
authors: awels
wiki_title: OVirt Engine Debug Obfuscated UI
wiki_revision_count: 19
wiki_last_updated: 2016-01-06
---

# OVirt Engine Debug Obfuscated UI

## Debug Obfuscated UI

### Owner

*   Name: [<NAME>](User:awels)
*   Email: <<EMAIL>>

### Introduction

Sometimes during the usage of the Web admin or User portal you will get a popup about an uncaught exception like this:

      Uncaught exception occurred. Please try reloading the page. Details:  [some information]

In general this message lets us know something went wrong, but is less than helpful in determining what exactly went wrong. The information provided usually includes some obfuscated code like 'c is null' or 'cannot get field O5d'. None of which is very helpful.

Why is this happening now? Recently we introduced some code that captures all exceptions that are not handled anywhere else, and displays it to the user. Before the un-handled exceptions would be written to the browser console and mostly ignored unless someone looked at the browser console. They are still written to the console, but they are also reported to the user, this has some benefits and some negatives. The benefits include the fact that the user can now report something is going wrong since they are being told. The negatives include the fact that the user sees the fact that something goes wrong and they conclude the product is bad. The developers cannot fix issues they are not aware of, so in the short term we will have more bug reports but in the long term we will have a better product due the more transparent exception reporting.

#### Debugging steps

#### Getting the full stack trace from the console

{'fraction_non_alphanumeric': 0.042710706150341685, 'fraction_numerical': 0.00683371298405467, 'mean_word_length': 4.388036809815951, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6033457', 'n_tokens_mistral': 889, 'n_tokens_neox': 847, 'n_words': 551}