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

[Distributed Debugger] Newly added breakpoint not works: Breakpoint in file that does not exist #48778

Open
StephanoGeorge opened this issue Nov 18, 2024 · 2 comments
Assignees
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@StephanoGeorge
Copy link

StephanoGeorge commented Nov 18, 2024

What happened + What you expected to happen

Steps to reproduce:

  • Write code, see below
  • Install VS Code extension: anyscalecompute.ray-distributed-debugger
  • Add cluster 127.0.0.1:8265, set local folder: /C:\Users\cheese\Codes\MyProject(C:\Users\cheese\Codes\MyProject, \C:\Users\cheese\Codes\MyProject cann't pass the absolute path check, /c/Users/cheese/Codes/MyProject will cause the tab opened when debugging to show that file not exist)
  • Run code
  • Wait and click debug button in ray extension
  • Click add breakpoint at the head of the line

What happened

The new breakpoint didn't work, and shows 'Breakpoint in file that does not exist':

image

Expected to happen

Newly added breakpoint works

Versions / Dependencies

Ray: 2.39.0

Python: 3.10.22 on WSL

OS: Windows 10

Ray Distributed Debugger: v0.1.3

Reproduction script

import ray

ray.init(
	runtime_env={
		"env_vars": {"RAY_DEBUG": "1"},
	}
)

@ray.remote
def my_task(x):
	y = x * x
	breakpoint()  # Add a breakpoint in the Ray task.
	for _ in range(10):
		y += 1
	return y

ray.get(my_task.remote(10))

Issue Severity

High: It blocks me from completing my task.

@StephanoGeorge StephanoGeorge added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Nov 18, 2024
@jcotant1 jcotant1 added the core Issues that should be addressed in Ray Core label Nov 18, 2024
@jjyao jjyao removed the core Issues that should be addressed in Ray Core label Nov 18, 2024
@jcotant1
Copy link
Collaborator

Hey @brucez-anyscale can you take a look at this one? Thank you

@pcmoritz
Copy link
Contributor

This would be @brycehuang30 not Bruce :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

4 participants