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

Alisa interface to Resolute has extra diagnostics #1300

Closed
reteprelief opened this Issue Jun 7, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@reteprelief
Contributor

reteprelief commented Jun 7, 2018

There are two cases:

  1. when the verification activity result status is set to the resolute result, it is also entered as a diagnostic, but should not.
  2. When Resolute executes a Fail expression it does not evaluate the fail text in the context of the throw, but the catch.

@reteprelief reteprelief added this to the 2.3.4 milestone Jun 7, 2018

@reteprelief reteprelief self-assigned this Jun 7, 2018

@wafflebot wafflebot bot added review and removed next labels Jun 7, 2018

@lwrage lwrage closed this in #1303 Jun 11, 2018

lwrage added a commit that referenced this issue Jun 11, 2018

#1300 Extra disgnostics in Resolute result presentation in ALISA (#1303)
* handling of fail expression messages in context of thrower to resolve
variable references. Should be fix in Resolute but I can do a local
override.

* Removed extra Diagnostic issues without text that were generated when we
set success or fail status on a verification activity, such as recordin
ghte result of a resolute or Java function.

@wafflebot wafflebot bot removed the review label Jun 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment