You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import edu.rice.cs.caper.bayou.annotations.Evidence;
public class TestIO1 {
void read(String file) {
Evidence.apicalls("readLine");
}
void foo(String file) {
Evidence.apicalls("readLine");
}
}
This leads to to two bad things:
The message "Unexpected error. Please retry." This is a bad error message. Bayou should return a message that clarifies that we only allow one hole in the code at one time, and Askbayou should deliver this message.
The "synthesize" button goes away. Note that this doesn't happen on successful termination, and it shouldn't happen in this error case either.
It seems like the same sorts of problems arise when we have a syntax error in the draft:
import edu.rice.cs.caper.bayou.annotations.Evidence;
public class TestIO1 {
// Read from a file
void read(String file) {
Evidence.apicalls("readLine")
}
}
The text was updated successfully, but these errors were encountered:
swaratchaudhuri
changed the title
"Unexpected error. Please retry." message when entering code with multiple holes
Bad error message when entering code with multiple holes
Jul 19, 2017
swaratchaudhuri
changed the title
Bad error message when entering code with multiple holes
Bad error message when entering code with multiple holes and code with syntax error
Jul 19, 2017
Commit 42fa463 addresses the search button not showing after an unexpected error. This was an artefact of the old UI where the error messages and search button were in the same place.
(This is closely related to issue #16.)
Here is some code I entered in Askbayou:
This leads to to two bad things:
The message "Unexpected error. Please retry." This is a bad error message. Bayou should return a message that clarifies that we only allow one hole in the code at one time, and Askbayou should deliver this message.
The "synthesize" button goes away. Note that this doesn't happen on successful termination, and it shouldn't happen in this error case either.
It seems like the same sorts of problems arise when we have a syntax error in the draft:
The text was updated successfully, but these errors were encountered: