Conversation
Member
Author
|
No idea why the formatting check failed. I did not change code in any of the modules mentioned besides key.ui and here locally a spotlessApply does not reformat anything. |
WolframPfeifer
approved these changes
Apr 29, 2026
Member
WolframPfeifer
left a comment
There was a problem hiding this comment.
I re-run the formatter task and it succeeds, I think it just crashed somehow (also, the log didn't show any formatting violation) ...
Regarding the assertion, I agree that we should remove it, since it crashes the GUI. I think this is a side effect from enabling the assertions by default. Maybe changing the if-else to enhanced switch could solve the problem for the future, since it has to cover all cases of the enum then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intended Change
Fixes a bug in the proof obligation browser.
When a proof is closed, the PO browser displays the corresponding closed icon inside the "Goto Proof" button. It happened that when selecting a PO, where the goal was closed by caching, the corresponding icon was not found causing an assertion failure. This renderes the browser unusable as it did not go to the corresponding proof and one could not open the dialog again.
This PR fixes this bug.
Type of pull request
Ensuring quality
Additional information and contact(s)
Maybe we should also replace the assertion with simple logging? In the worst case the button would display the wrong close icon.
The contributions within this pull request are licensed under GPLv2 (only) for inclusion in KeY.