-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix trace state parsing. #638
Fix trace state parsing. #638
Conversation
- Without this the `.Value<string>` was exploding attempting to convert to a string.
Codecov Report
@@ Coverage Diff @@
## master #638 +/- ##
==========================================
- Coverage 72.89% 69.37% -3.53%
==========================================
Files 257 257
Lines 12576 12580 +4
Branches 848 848
==========================================
- Hits 9167 8727 -440
- Misses 3409 3583 +174
- Partials 0 270 +270
Continue to review full report at Codecov.
|
@NTaylorMullen just out of curiosity, can I see how this was failing for you? In case something similar crops up in PowerShell Editor Services 😆 |
I have it all patched locally so not easy to reproduce but it was a Cast exception. The gist is that when you got a jsonrpc payload which had:
If you have the powershell language server running in VS you'll see the exception too (they provide tracing); although I don't believe VSCode's jsonrpc bits do. |
Oh interesting, not sure I was using |
Ah yes this PR: #553 |
Taylor, do you think your PR will fix #609 too? |
Yup, absolutely will fix that! |
.Value<string>
was exploding attempting to convert to a string.