Skip to content
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

Bug report: Baking after resolving a ingredient error with a set of multiple operations operates on the wrong data. #329

Closed
picapi opened this issue Aug 12, 2018 · 1 comment
Assignees
Labels

Comments

@picapi
Copy link
Contributor

picapi commented Aug 12, 2018

Summary

When using multiple operations, if an intermediary operation has an error, the first bake after this error is corrected will operate on the error text output, rather than the true given input. This could result in misleading outputs while attempting to operate on data.

Example

Click here and then change the key to become a single character. The expectation would be that the output would be each word in the input enciphered using the key on a different line, but the reality is that the No Key Entered message is enciphered, and remains in the output until a second character is utilised.

@picapi picapi changed the title Bug report:Baking after resolving a ingredient error with a set of multiple operations operates on the wrong data. Bug report: Baking after resolving a ingredient error with a set of multiple operations operates on the wrong data. Aug 12, 2018
@d98762625 d98762625 added the bug label Aug 13, 2018
@n1474335 n1474335 self-assigned this Aug 19, 2018
@n1474335
Copy link
Member

Thanks very much for raising this @picapi. It was a very easy fix, but it looks like it's been there for a while. Good spot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants