8000 [core] Returning a useful message when trying to get logs for a job that has not started yet by israbbani · Pull Request #53174 · ray-project/ray · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[core] Returning a useful message when trying to get logs for a job that has not started yet #53174

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

israbbani
Copy link
Contributor

[core] Returning a useful message when trying to get logs for a job that has not been started yet.

This was reported by an OSS user.

has not been started yet.

Signed-off-by: irabbani <irabbani@anyscale.com>
@israbbani israbbani added the go add ONLY when ready to merge, run all tests label May 20, 2025
@israbbani israbbani changed the title [core] Returning a useful message when trying to get logs for a job that [core] Returning a useful message when trying to get logs for a job that has not started yet May 20, 2025
@israbbani israbbani marked this pull request as ready for review May 20, 2025 18:36
@israbbani israbbani requested a review from a team May 20, 2025 18:59
@@ -145,8 +145,13 @@ async def _resolve_job_filename(self, sub_job_id: str) -> Tuple[str, str]:
logger.info(f"Submission job ID {sub_job_id} not found.")
return None, None

node_id = job_info.driver_node_id
node_id = target_job.driver_node_id
Copy link
Collaborator

Choose a reason for hiding this comment

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

qq: was this fixing a bug? does it make sense to write a quick unittest for this function

Copy link
Collaborator
@edoakes edoakes left a comment

Choose a reason for hiding this comment

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

How's this intended to be consumed? Job CLI, REST API, dashboard? (or all of the above)

Comment on lines +150 to +154
if target_job.status == JobStatus.PENDING:
raise ValueError(
f"Job {sub_job_id} is still {JobStatus.PENDING}."
"Since it has not started yet, there are no logs available yet."
)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I believe this will result in a 500 internal server error (which is not ideal)

Copy link

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.

@github-actions github-actions bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests stale The issue is stale. It will be closed within 7 days unless there are further conversation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0