This repository was archived by the owner on Dec 18, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 448
NullReferenceException when logging as Trace and an argument is null #1005
Comments
Nice, so we should probably handle null arguments |
Yes. I did not notice but when I pressed Ctrl+C Console.ReadLine() returned null which I tried to send and got the exception. I think we should review logging since I think I saw the same pattern in at least one more place. |
moozzyk
pushed a commit
that referenced
this issue
Oct 25, 2017
Storing exception thrown during parameter binding and rethrowing when the method is about to throw. This allows completing invocations with a HubException and keeping the connection open. We will also no longer close the connection if parameters for client side methods cannot be bound. We will log and continue. Fixes: #818 (Also fixing #1005 because I was just touching this line)
moozzyk
pushed a commit
that referenced
this issue
Oct 25, 2017
Storing exception thrown during parameter binding and rethrowing when the method is about to throw. This allows completing invocations with a HubException and keeping the connection open. We will also no longer close the connection if parameters for client side methods cannot be bound. We will log and continue. Fixes: #818 (Also fixing #1005 because I was just touching this line)
moozzyk
added a commit
that referenced
this issue
Oct 30, 2017
Late parameter binding Storing exception thrown during parameter binding and rethrowing when the method is about to throw. This allows completing invocations with a HubException and keeping the connection open. We will also no longer close the connection if parameters for client side methods cannot be bound. We will log and continue. Fixes: #818 (Also fixing #1005 because I was just touching this line)
Fixed in 18f770e |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
here.
The text was updated successfully, but these errors were encountered: