Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(linter): memorize visited block id in neighbors_filtered_by_edge_weight #3407

Conversation

mysteryven
Copy link
Member

@mysteryven mysteryven commented May 25, 2024

closes: #3396

we visit the same node too many times, I picked some result from run require-render-return rule on timeserieseexploere.js

    NodeIndex(64): 368640,
    NodeIndex(67): 737280,
    NodeIndex(70): 2949120,
    NodeIndex(73): 5971968,
    NodeIndex(76): 11943936,
    NodeIndex(43): 184320,
    NodeIndex(71): 2985984,
    NodeIndex(65): 368640,
    NodeIndex(68): 1474560,
    NodeIndex(74): 5971968,
    NodeIndex(77): 23887872,
    NodeIndex(44): 184320,
    NodeIndex(41): 73728,
    NodeIndex(35): 36864,
    NodeIndex(66): 737280,
    NodeIndex(69): 1474560,
    NodeIndex(72): 2985984,
    NodeIndex(75): 11943936,

Copy link

graphite-app bot commented May 25, 2024

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

@github-actions github-actions bot added A-linter Area - Linter A-semantic Area - Semantic labels May 25, 2024
Copy link

codspeed-hq bot commented May 25, 2024

CodSpeed Performance Report

Merging #3407 will not alter performance

Comparing 05-24-fix_linter_memorize_visited_block_id_in_neighbors_filtered_by_edge_weight_ (5e06298) with main (3855579)

Summary

✅ 22 untouched benchmarks

@rzvxa rzvxa force-pushed the 05-24-fix_linter_memorize_visited_block_id_in_neighbors_filtered_by_edge_weight_ branch from f068f7a to 170f5bb Compare May 25, 2024 12:25
@rzvxa
Copy link
Collaborator

rzvxa commented May 25, 2024

@mysteryven I didn't mean to force push here, I just stacked my PR on top of it, Didn't know it would result in this sorry about it.

@rzvxa
Copy link
Collaborator

rzvxa commented May 25, 2024

Well now that the cat is out of the bag, I may as well go ahead and restack it properly doing the appropriate CFG changes. Sorry for the inconvenience!

@mysteryven mysteryven force-pushed the 05-24-fix_linter_memorize_visited_block_id_in_neighbors_filtered_by_edge_weight_ branch from 3e830d1 to ee57dab Compare May 26, 2024 07:14
@mysteryven mysteryven marked this pull request as ready for review May 26, 2024 07:18
@Boshen Boshen added the merge label May 26, 2024
Copy link

graphite-app bot commented May 26, 2024

Merge activity

  • May 26, 4:01 AM EDT: The merge label 'merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • May 26, 4:11 AM EDT: Boshen added this pull request to the Graphite merge queue.
  • May 26, 4:15 AM EDT: Boshen merged this pull request with the Graphite merge queue.

@Boshen Boshen force-pushed the 05-24-fix_linter_memorize_visited_block_id_in_neighbors_filtered_by_edge_weight_ branch 2 times, most recently from 917f3ec to c232751 Compare May 26, 2024 08:05
@Boshen
Copy link
Member

Boshen commented May 26, 2024

I screwed up the rebase 🤔

…_weight` (#3407)

closes: #3396

we visit the same node too many times, I picked some result from run require-render-return rule on [timeserieseexploere.js](https://github.com/elastic/kibana/blob/main/x-pack/plugins/ml/public/application/timeseriesexplorer/timeseriesexplorer.js)

```bash
    NodeIndex(64): 368640,
    NodeIndex(67): 737280,
    NodeIndex(70): 2949120,
    NodeIndex(73): 5971968,
    NodeIndex(76): 11943936,
    NodeIndex(43): 184320,
    NodeIndex(71): 2985984,
    NodeIndex(65): 368640,
    NodeIndex(68): 1474560,
    NodeIndex(74): 5971968,
    NodeIndex(77): 23887872,
    NodeIndex(44): 184320,
    NodeIndex(41): 73728,
    NodeIndex(35): 36864,
    NodeIndex(66): 737280,
    NodeIndex(69): 1474560,
    NodeIndex(72): 2985984,
    NodeIndex(75): 11943936,
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter A-semantic Area - Semantic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

linter: react/require-render-return hangs
3 participants