Skip to content

Conversation

@Draklos
Copy link
Contributor

@Draklos Draklos commented Dec 17, 2025

No description provided.

@Draklos Draklos force-pushed the master branch 3 times, most recently from 6f0a495 to 115cac3 Compare December 23, 2025 15:23
data: stats.map(a => [a[0], a[3]]),
atomic_queue_stats: stats,
data: stats.map((a) => {
const [mean, stdev, min, max] = [a[3], a[4], a[1], a[2]].map(prec0);
Copy link
Owner

Choose a reason for hiding this comment

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

It should map over a[1:] slice. Indexing individual elements of a defeats the purpose of using map.

What is the intention behind this absurd order of identifiers in the destructuring statement?

<span class="tooltip_scalability_title">${n_threads} producers, ${n_threads} consumers</span>
const { x, points } = this;
const rows = points
.filter(({ series }) => series.visible)
Copy link
Owner

Choose a reason for hiding this comment

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

I don't think disabled series elements are present in the points array. Am I wrong?

const rows = points
.filter(({ series }) => series.visible)
.map(point => point.options.tooltip_row)
.join('');
Copy link
Owner

Choose a reason for hiding this comment

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

For easy unanticipated debugging it is best for tooltip html to be nicely formatted for best readability. E.g. when you hover your mouse over rows variable in the debugger, often accidentally, you don't want to see all rows packed into one huge unreadable line, do you?

@Draklos
Copy link
Contributor Author

Draklos commented Dec 23, 2025

Thank you for the review! The changes to the remarks have been pushed.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants