Skip to content

Fix bug in ProofManagementDialog#3812

Merged
unp1 merged 2 commits intomainfrom
fixProofObligationBrowser
Apr 29, 2026
Merged

Fix bug in ProofManagementDialog#3812
unp1 merged 2 commits intomainfrom
fixProofObligationBrowser

Conversation

@unp1
Copy link
Copy Markdown
Member

@unp1 unp1 commented Apr 28, 2026

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

  • Bug fix (non-breaking change which fixes an issue)

Ensuring quality

  • I have tested the feature as follows: Closed a proof by caching, open the dialog, selected the closed PO: no exception thrown, Goto Proof worked and PO browser could be used again afterwards

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.

@unp1
Copy link
Copy Markdown
Member Author

unp1 commented Apr 28, 2026

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.

@unp1 unp1 self-assigned this Apr 28, 2026
@unp1 unp1 added the 🐞 Bug label Apr 28, 2026
@unp1 unp1 added this to the v3.0.0 milestone Apr 28, 2026
Copy link
Copy Markdown
Member

@WolframPfeifer WolframPfeifer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@unp1 unp1 enabled auto-merge April 29, 2026 11:30
@unp1 unp1 added this pull request to the merge queue Apr 29, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 29, 2026
@unp1 unp1 added this pull request to the merge queue Apr 29, 2026
Merged via the queue into main with commit 123ca74 Apr 29, 2026
69 of 70 checks passed
@unp1 unp1 deleted the fixProofObligationBrowser branch April 29, 2026 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants