-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Tests in in Test Explorer are seen but do nothing with a symlinked folder #23223
Comments
Hi! Sorry for the delay, I was on vacation, will take a look at this shortly |
Hi! Was looking through this and tried both with: in both it successfully discovered and run the tests. Could you send along your full python logs? And also confirm you are the most recent version of the extension (pre-release). Thanks |
Hi, thanks for getting back. First, I still can't add comments in #22018 Second, I believe this issue #23224 may be somehow related. I'm using your The scenario with the issue is this, you must use Mac iCloud folder (I testes with
Do You may Delete and Recreate, choose any python version you like. In a Terminal (be sure to see pip install pytest Go to Now, to reproduce the issue I'm seeing: I have in my home folder (
Then: code ~/Projects/cwd_specified/ You need to set up the Python Interpreter again, choose the one already created and go to Test Explorer. Try to run the tests, nothing happens. |
Aha! I think I have found it. My edit to support symlinks only checked to see if the cwd was a symlink which does not work if the child directory is a cwd. So in your example the symlink is the parent directory of the workspace cwd (where you open the workspace on cwd_specified) which means my added code is not catching it.
working on a fix now! Thank you for all your help!! Fingers crossed this fixes the bug. |
Hello! I have put in a fix for this issue and it should now be working! If you could try it on the newest version of the python extension nightly pre-release that would be great so we know if it works! Happy coding! |
So sorry this is long, wrote steps best I could and hopefully this will help!! Let me know if you have any questions
|
@eleanorjboyd I can finally confirm that it's all working as expected at least in VSCode:
Many thanks! |
So pumped to hear this! Thanks for all the responses / engagement to get this fix |
Type: Bug
It's still about #22658 (comment)
I have this symlink:
/Users/alan/Projects -> '/Users/alan/Library/Mobile Documents/com~apple~CloudDocs/Projects'
And my project
~/Projects/face-ai
when opened with VScode:code ~/Projects/face-ai
seems all fine except that running the Tests does not do anything!
If I open with original path:
code "/Users/alan/Library/Mobile Documents/com~apple~CloudDocs/Projects/face-ai"
Everything works fine.
I suspect that the
whitespace
in the symlink can be the cause.I cannot change
/Users/alan/Library/Mobile Documents/com~apple~CloudDocs
beacuse this is from macOS and it's the place foriClouds
, where I keep my projects backed up in the cloud.Extension version: 2024.4.1
VS Code version: Code 1.88.0 (5c3e652f63e798a5ac2f31ffd0d863669328dc4c, 2024-04-03T13:28:09.495Z)
OS version: Darwin arm64 23.4.0
Modes:
Remote OS version: Linux x64 5.4.0-91-generic
Connection to 'SSH: toverdrive' could not be established Canceled
Connection to 'SSH: toverdrive' could not be established Canceled
Connection to 'SSH: toverdrive' could not be established Canceled
python.languageServer
setting: DefaultUser Settings
Installed Extensions
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
Connection to 'SSH: toverdrive' could not be established Canceled
Connection to 'SSH: toverdrive' could not be established Canceled
Connection to 'SSH: toverdrive' could not be established Canceled
A/B Experiments
The text was updated successfully, but these errors were encountered: