-
Notifications
You must be signed in to change notification settings - Fork 492
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
Extended logic eval error #2975
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2975 +/- ##
==========================================
+ Coverage 47.61% 47.62% +0.01%
==========================================
Files 358 358
Lines 57906 57928 +22
==========================================
+ Hits 27570 27589 +19
- Misses 27208 27212 +4
+ Partials 3128 3127 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the pc is set to the end or maybe even 1 past the end for errors that don't get detected until after the first pass (when jumps are resolved). Could you put in a test to show things work ok when PcDetails is called then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems pretty clear you would just get an empty string, so that seems ok.
d60cfba
to
b351f0a
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good.
Summary
Return a bit more details on eval failure for app calls.
Test Plan
Added
EvalContext.PcDetails()
method and tests.