7482: Confusing display of stack traces when selecting event types with no events

[jpbempel]

…th no events

In EventBrowser page, when there is no selection all events are
considered but if there is a selection we filtered events based on
this selection event if there is no events

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7482: Confusing display of stack traces when selecting event types with no events

Reviewers

• Alex Macdonald (@aptmac - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/344/head:pull/344
$ git checkout pull/344

Update a local copy of the PR:
$ git checkout pull/344
$ git pull https://git.openjdk.java.net/jmc pull/344/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 344

View PR using the GUI difftool:
$ git pr show -t 344

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/344.diff

[bridgekeeper]

👋 Welcome back jpbempel! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (db53724a)

[openjdk]

@jpbempel This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7482: Confusing display of stack traces when selecting event types with no events

Reviewed-by: aptmac

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• f077a40: 7493: Update versions and copyright on Update site pages

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[thegreystone]

@jpbempel - this is ready to integrate - @aptmac is a reviewer now. :)

[jpbempel]

/integrate

[openjdk]

Going to push as commit ce10e3f.
Since your change was applied there have been 2 commits pushed to the master branch:

• b65e351: 7494: Unable to view JMC Help Contents
• f077a40: 7493: Update versions and copyright on Update site pages

Your commit was automatically rebased without conflicts.

[openjdk]

@jpbempel Pushed as commit ce10e3f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.