Skip to content

Conversation

@kyuds
Copy link
Contributor

@kyuds kyuds commented Oct 29, 2025

Description

Rich progress currently doesn't support reporting progress from worker. As this is expected to take a lot of design into consideration, default to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set use_ray_tqdm, so the requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:

  • rich progress bars enabled
  • use_ray_tqdm disabled.

Related issues

Fixes #58250

Additional information

N/A

@kyuds kyuds requested a review from a team as a code owner October 29, 2025 07:09
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly defaults to tqdm_ray for progress reporting from workers by disabling rich progress bars when use_ray_tqdm is enabled. The logic is cleanly refactored into the _use_rich_progress method, centralizing the decision-making. I have one suggestion to improve the logging behavior for better user feedback.

Signed-off-by: kyuds <[email protected]>
@kyuds kyuds changed the title [Data] Default to tqdm_ray for progress reporting from worker [Data] Use tqdm_ray for progress reporting from worker Oct 29, 2025
Signed-off-by: Daniel Shin <[email protected]>
@kyuds
Copy link
Contributor Author

kyuds commented Oct 29, 2025

PTAL @goutamvenkat-anyscale ! Thank you in advance!

Signed-off-by: Daniel Shin <[email protected]>
cursor[bot]

This comment was marked as outdated.

@ray-gardener ray-gardener bot added data Ray Data-related issues community-contribution Contributed by the community labels Oct 29, 2025
@goutamvenkat-anyscale goutamvenkat-anyscale added the go add ONLY when ready to merge, run all tests label Oct 29, 2025
@goutamvenkat-anyscale
Copy link
Contributor

lgtm!

@kyuds
Copy link
Contributor Author

kyuds commented Oct 30, 2025

PTAL @goutamvenkat-anyscale ! I think this is ready to merge! (previous test fail was either flaky or was fixed by updating to latest master) Thank you in advance 🙏

@gvspraveen gvspraveen requested a review from raulchen November 2, 2025 04:31
@raulchen raulchen merged commit e995456 into ray-project:master Nov 5, 2025
6 checks passed
YoussefEssDS pushed a commit to YoussefEssDS/ray that referenced this pull request Nov 8, 2025
…#58277)

## Description
Rich progress currently doesn't support reporting progress from worker.
As this is expected to take a lot of design into consideration, default
to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set `use_ray_tqdm`, so the
requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:
- rich progress bars enabled
- use_ray_tqdm disabled.

## Related issues
Fixes ray-project#58250

## Additional information
N/A

---------

Signed-off-by: kyuds <[email protected]>
Signed-off-by: Daniel Shin <[email protected]>
@kyuds kyuds deleted the progress-worker-case branch November 8, 2025 01:53
landscapepainter pushed a commit to landscapepainter/ray that referenced this pull request Nov 17, 2025
…#58277)

## Description
Rich progress currently doesn't support reporting progress from worker.
As this is expected to take a lot of design into consideration, default
to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set `use_ray_tqdm`, so the
requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:
- rich progress bars enabled
- use_ray_tqdm disabled.

## Related issues
Fixes ray-project#58250

## Additional information
N/A

---------

Signed-off-by: kyuds <[email protected]>
Signed-off-by: Daniel Shin <[email protected]>
Aydin-ab pushed a commit to Aydin-ab/ray-aydin that referenced this pull request Nov 19, 2025
…#58277)

## Description
Rich progress currently doesn't support reporting progress from worker.
As this is expected to take a lot of design into consideration, default
to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set `use_ray_tqdm`, so the
requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:
- rich progress bars enabled
- use_ray_tqdm disabled.

## Related issues
Fixes ray-project#58250

## Additional information
N/A

---------

Signed-off-by: kyuds <[email protected]>
Signed-off-by: Daniel Shin <[email protected]>
Signed-off-by: Aydin Abiar <[email protected]>
ykdojo pushed a commit to ykdojo/ray that referenced this pull request Nov 27, 2025
…#58277)

## Description
Rich progress currently doesn't support reporting progress from worker.
As this is expected to take a lot of design into consideration, default
to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set `use_ray_tqdm`, so the
requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:
- rich progress bars enabled
- use_ray_tqdm disabled.

## Related issues
Fixes ray-project#58250

## Additional information
N/A

---------

Signed-off-by: kyuds <[email protected]>
Signed-off-by: Daniel Shin <[email protected]>
Signed-off-by: YK <[email protected]>
SheldonTsen pushed a commit to SheldonTsen/ray that referenced this pull request Dec 1, 2025
…#58277)

## Description
Rich progress currently doesn't support reporting progress from worker.
As this is expected to take a lot of design into consideration, default
to using tqdm progress (which supports progress reporting from worker)

furthermore, we don't have an auto-detect to set `use_ray_tqdm`, so the
requirement is for that to be disabled as well.

In summary, requirements for rich progress as of now:
- rich progress bars enabled
- use_ray_tqdm disabled.

## Related issues
Fixes ray-project#58250

## Additional information
N/A

---------

Signed-off-by: kyuds <[email protected]>
Signed-off-by: Daniel Shin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contributed by the community data Ray Data-related issues go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Data] - Rich Progress bar doesn't render during execution for Train

4 participants