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

Precompute the rank of a data node in all the scenario config DAGs. #2072

Merged
merged 21 commits into from
Dec 9, 2024

Conversation

jrobinAV
Copy link
Member

@jrobinAV jrobinAV commented Oct 16, 2024

resolves #2071

  • Each data node configuration now has a _rank attribute as a dictionary.
  • When configuring a new scenario configuration, all the nested data node configurations are updated. An entry is added in the DataNodeConfig._rank dictionary. The key is the scenario config ID, and the value is the rank of the data node in the scenario config DAG.
  • Each data node exposes a hidden API to retrieve its _rank for a given scenario configuration.

FlorianJacta
FlorianJacta previously approved these changes Oct 16, 2024
Copy link
Member

@FlorianJacta FlorianJacta left a comment

Choose a reason for hiding this comment

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

I agree with the principle. I let the others review the code 😄

@jrobinAV jrobinAV added Core Related to Taipy Core 🖰 GUI Related to GUI 🟨 Priority: Medium Not blocking but should be addressed labels Oct 16, 2024
@jrobinAV jrobinAV self-assigned this Oct 16, 2024
FredLL-Avaiga
FredLL-Avaiga previously approved these changes Oct 17, 2024
Copy link
Member

@FredLL-Avaiga FredLL-Avaiga left a comment

Choose a reason for hiding this comment

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

with comment

taipy/core/config/scenario_config.py Outdated Show resolved Hide resolved
Copy link
Contributor

github-actions bot commented Oct 17, 2024

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
19485 16951 87% 0% 🟢

New Files

No new covered files...

Modified Files

File Coverage Status
taipy/core/config/data_node_config.py 99% 🟢
taipy/core/config/scenario_config.py 88% 🟢
taipy/core/data/data_node.py 98% 🟢
taipy/gui_core/_adapters.py 53% 🟢
taipy/gui_core/_context.py 62% 🟢
taipy/gui_core/filters.py 67% 🟢
TOTAL 78% 🟢

updated for commit: 59afe69 by action🐍

@FredLL-Avaiga FredLL-Avaiga self-assigned this Oct 17, 2024
Copy link
Member

@trgiangdo trgiangdo left a comment

Choose a reason for hiding this comment

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

Minor comments

taipy/core/data/data_node.py Outdated Show resolved Hide resolved
taipy/core/data/data_node.py Outdated Show resolved Hide resolved
@FredLL-Avaiga FredLL-Avaiga force-pushed the feature/#2071-rank-datanodes-in-selector branch from 1c622f9 to dbd2949 Compare October 22, 2024 08:26
trgiangdo
trgiangdo previously approved these changes Oct 31, 2024
Copy link
Member

@trgiangdo trgiangdo left a comment

Choose a reason for hiding this comment

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

LGTM

toan-quach
toan-quach previously approved these changes Oct 31, 2024
Copy link
Member

@toan-quach toan-quach left a comment

Choose a reason for hiding this comment

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

lgtm :D

@jrobinAV
Copy link
Member Author

Actually LNGTM.

I don't like it, and I'm having difficulty explaining why. Please give me some time to figure it out.

Copy link
Contributor

This PR has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this PR, then please add new commit or another comment, otherwise this PR will be closed in 14 days. For more information please refer to the contributing guidelines.

@github-actions github-actions bot added the 🥶Waiting for contributor Issues or PRs waiting for a long time label Nov 14, 2024
@FredLL-Avaiga FredLL-Avaiga removed the 🥶Waiting for contributor Issues or PRs waiting for a long time label Nov 14, 2024
@jrobinAV jrobinAV marked this pull request as draft November 27, 2024 11:43
@jrobinAV jrobinAV dismissed stale reviews from trgiangdo and toan-quach via 3ba5c9c November 27, 2024 12:32
Copy link
Contributor

github-actions bot commented Nov 29, 2024

Coverage report for ./frontend/taipy

Caution

Coverage does not meet threshold
Statements coverage not met for global: expected >=80%, but got 51.87376725838264%

St.
Category Percentage Covered / Total
🔴 Statements
51.87% (-0.21% 🔻)
263/507
🔴 Branches
21.61% (-0.14% 🔻)
67/310
🔴 Functions 14.66% 17/116
🔴 Lines
53.19% (-0.23% 🔻)
242/455
Show files with reduced coverage 🔻
St.
File Statements Branches Functions Lines
🔴 CoreSelector.tsx
31.32% (-0.24% 🔻)
15.53% (-0.15% 🔻)
15.38%
33.33% (-0.28% 🔻)

Test suite run success

7 tests passing in 1 suite.

Report generated by 🧪jest coverage report action from 59afe69

Co-authored-by: Jean-Robin <jeanrobin.medori@avaiga.com>
@jrobinAV jrobinAV marked this pull request as ready for review December 3, 2024 09:06
Copy link
Contributor

github-actions bot commented Dec 3, 2024

Coverage report for ./frontend/taipy-gui

Caution

Coverage does not meet threshold
Branches coverage not met for global: expected >=80%, but got 69.12402428447528%

St.
Category Percentage Covered / Total
🟢 Statements 87.36% 3468/3970
🟡 Branches 69.12% 2391/3459
🟢 Functions 83.16% 642/772
🟢 Lines 87.82% 3210/3655

Test suite run success

701 tests passing in 47 suites.

Report generated by 🧪jest coverage report action from 59afe69

@jrobinAV jrobinAV merged commit dd9f3ad into develop Dec 9, 2024
133 checks passed
@jrobinAV jrobinAV deleted the feature/#2071-rank-datanodes-in-selector branch December 9, 2024 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Related to Taipy Core 🖰 GUI Related to GUI 🟨 Priority: Medium Not blocking but should be addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rank data nodes by topological order in the data node selector
5 participants