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

pydev debugger: critical: unable to get real case for file #260

Open
Tisten opened this issue Aug 29, 2023 · 0 comments
Open

pydev debugger: critical: unable to get real case for file #260

Tisten opened this issue Aug 29, 2023 · 0 comments

Comments

@Tisten
Copy link

Tisten commented Aug 29, 2023

I'm using pydevd to debug whilst running NVidia's "Omniverse". When launching the application I'm getting this error in the log, asking me to create a ticket in the tracker. I hope this is the tracker which the logging refers to.

The log says:

0.00s - pydev debugger: critical: unable to get real case for file. Details:
filename: c:\dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py
drive: C:
parts: ['\\dev\\apps\\code\\extscache\\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\\debugpy\\_vendored\\pydevd\\pydevd_file_utils.py']
(please create a ticket in the tracker to address this).
Traceback (most recent call last):
  File "c:\dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 168, in _resolve_listing_parts
    return _resolve_listing(resolved, iter(parts_in_lowercase))
  File "c:\dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 158, in _resolve_listing
    raise FileNotFoundError('Unable to find: %s in %s. Dir Contents: %s' % (
FileNotFoundError: Unable to find: \dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py in C:. Dir Contents: ['Apps', 'assets', 'binaries', 'exts', 'omniUsdaWatcher_29416.log', 'omniUsdaWatcher_32208.log', 'omniUsdaWatcher_48792.log']

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "c:\dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 173, in _resolve_listing_parts
    return _resolve_listing(resolved, iter(parts_in_lowercase))
  File "c:\dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py", line 158, in _resolve_listing
    raise FileNotFoundError('Unable to find: %s in %s. Dir Contents: %s' % (
FileNotFoundError: Unable to find: \dev\apps\code\extscache\omni.kit.debug.python-0.2.1+049bdbc3.wx64.r.cp310\debugpy\_vendored\pydevd\pydevd_file_utils.py in C:. Dir Contents: ['Apps', 'assets', 'binaries', 'exts', 'omniUsdaWatcher_29416.log', 'omniUsdaWatcher_32208.log', 'omniUsdaWatcher_48792.log']

I'm running this on Windows, and the code folder is actually a junction, so if I from cmd.exe got to C:\dev\apps and write dir then I get:

 Directory of C:\Dev\Apps

2023-08-28  11:15    <DIR>          .
2023-08-29  13:54    <DIR>          ..
2023-08-14  08:18    <JUNCTION>     code [C:\packman-repo\chk\code-launcher\2023.1.1-beta.3+2023.1.682.e681c8a8.tc.windows-x86_64.release.signed]

The Dir Contents listed is from the applications working dir which happens to be C:\Dev

The pydevd version used by default is 2.8.0. But I upgraded to 2.9.6 to see if it was fixed. I got the log above from 2.9.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant