Skip to content

6832: Should allow plotting line charts for all quantities#688

Closed
aymane-harmaz wants to merge 4 commits intoopenjdk:masterfrom
aymane-harmaz:6832
Closed

6832: Should allow plotting line charts for all quantities#688
aymane-harmaz wants to merge 4 commits intoopenjdk:masterfrom
aymane-harmaz:6832

Conversation

@aymane-harmaz
Copy link
Copy Markdown
Member

@aymane-harmaz aymane-harmaz commented Nov 24, 2025

This PR makes sure line charts cover all the events across multiple IItemIterables, and makes it possible for linear quantities to be represented as line charts on custom pages.


Progress

  • Commit message must refer to an issue
  • Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

  • JMC-6832: Should allow plotting line charts for all quantities (Bug - P2)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/688/head:pull/688
$ git checkout pull/688

Update a local copy of the PR:
$ git checkout pull/688
$ git pull https://git.openjdk.org/jmc.git pull/688/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 688

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/688.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Nov 24, 2025

👋 Welcome back aharmaz! 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.

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Nov 24, 2025

@aymane-harmaz 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:

6832: Should allow plotting line charts for all quantities

Reviewed-by: hirt

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 4 new commits pushed to 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.

@openjdk openjdk Bot added the rfr label Nov 24, 2025
@mlbridge
Copy link
Copy Markdown

mlbridge Bot commented Nov 24, 2025

Webrevs

@thegreystone
Copy link
Copy Markdown
Member

This one effectively doubles the memory usage. For solving this and the sorting, perhaps a specialized merge sort iterator could be used instead?

@aymane-harmaz aymane-harmaz marked this pull request as draft December 4, 2025 10:55
@openjdk openjdk Bot removed the rfr label Dec 4, 2025
@aymane-harmaz aymane-harmaz marked this pull request as ready for review January 19, 2026 18:29
@openjdk openjdk Bot added the rfr label Jan 19, 2026
public T peek() {
if (!this.hasPeeked) {
this.hasPeeked = true;
this.peekedElement = this.sourceIterator.next();
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should there be a hasNext() check here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yes, thanks for pointing that out, I have added the check in both peek() and next()

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Feb 2, 2026

@aymane-harmaz Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@bridgekeeper
Copy link
Copy Markdown

bridgekeeper Bot commented Mar 2, 2026

@aymane-harmaz This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@aymane-harmaz
Copy link
Copy Markdown
Member Author

/keepalive

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Mar 5, 2026

@aymane-harmaz The pull request is being re-evaluated and the inactivity timeout has been reset.

@openjdk openjdk Bot added the ready label Mar 11, 2026
@aymane-harmaz
Copy link
Copy Markdown
Member Author

/integrate

@openjdk
Copy link
Copy Markdown

openjdk Bot commented Mar 12, 2026

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk Bot added the integrated label Mar 12, 2026
@openjdk openjdk Bot closed this Mar 12, 2026
@openjdk
Copy link
Copy Markdown

openjdk Bot commented Mar 12, 2026

@aymane-harmaz Pushed as commit 8d51efa.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants