Exceptionless.UI icon indicating copy to clipboard operation
Exceptionless.UI copied to clipboard

Indent inner errors respectively and show inner data

Open niemyjski opened this issue 9 years ago • 5 comments

all Inner errors share the same indention, they should be indented to match there inner depth level. Doing so would clear up some confusion.

niemyjski avatar Jan 20 '16 21:01 niemyjski

https://be.exceptionless.io/event/569fa37145abcb197cd8a703 Generated from

try
            {
                try
                {
                    try
                    {
                        throw new ArgumentException("This is the inner argument exception", "wrongArg");
                    }
                    catch (Exception e1)
                    {
                        throw new TargetInvocationException("Target invocation exception. Blah blah blah blah.", e1);
                    }
                }
                catch (Exception e2)
                {
                    throw new TargetInvocationException("Outer Exception. This is some text of the outer exception.", e2);
                }
            }
            catch (Exception exception)
            {
                exception.ToExceptionless().Submit();
            }

niemyjski avatar Jan 20 '16 22:01 niemyjski

Actual stack trace:

System.Reflection.TargetInvocationException: Outer Exception. This is some text of the outer exception. ---> System.Reflection.TargetInvocationException: Target invocation exception. Blah blah blah blah. ---> System.ArgumentException: This is the inner argument exception
Parametername: wrongArg
   bei ExceptionlessTest.Program.Main(String[] args) in c:\Users\febersol\Documents\Visual Studio 2013\Projects\ExceptionlessTest\ExceptionlessTest\Program.cs:Zeile 22.
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei ExceptionlessTest.Program.Main(String[] args) in c:\Users\febersol\Documents\Visual Studio 2013\Projects\ExceptionlessTest\ExceptionlessTest\Program.cs:Zeile 26.
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei ExceptionlessTest.Program.Main(String[] args) in c:\Users\febersol\Documents\Visual Studio 2013\Projects\ExceptionlessTest\ExceptionlessTest\Program.cs:Zeile 31.

Output in the UI:

System.Reflection.TargetInvocationException: Outer Exception. This is some text of the outer exception.
 ---> System.Reflection.TargetInvocationException: Target invocation exception. Blah blah blah blah.
 ---> System.ArgumentException: This is the inner argument exception Parametername: wrongArg
at ExceptionlessTest.Program.Main() in c:\Users\febersol\Documents\Visual Studio 2013\Projects\ExceptionlessTest\ExceptionlessTest\Program.cs:line 26:col 25
--- End of inner exception stack trace ---
at ExceptionlessTest.Program.Main(System.String[] args) at offset 79 in c:\Users\febersol\Documents\Visual Studio 2013\Projects\ExceptionlessTest\ExceptionlessTest\Program.cs:line 31:col 21

Please note that Program.cs:line 22 (where the innermost exception is thrown) isn't shown.

frankebersoll avatar Jan 21 '16 09:01 frankebersoll

Also looks like we are missing the string arguments as well.

niemyjski avatar Jan 21 '16 16:01 niemyjski

This seems to be a problem in the serializer in our .NET client. Added a failing test in exceptionless/exceptionless.net@4b3127571df6ea8827390690752a93589001b41e

frankebersoll avatar Jan 22 '16 00:01 frankebersoll

https://github.com/exceptionless/Exceptionless.UI/issues/59

niemyjski avatar Sep 23 '16 22:09 niemyjski

This should be fixed due to inner errors.

niemyjski avatar Mar 06 '23 13:03 niemyjski