Skip to content

Python can run directly in the terminal, but can't be debugged with F5 #301

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

Closed
LongQIByte opened this issue Mar 20, 2019 · 4 comments
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@LongQIByte
Copy link

I just saw #210 in the issue, but I still haven't modified the problem. When I debugged it, it didn't report an error, but it didn't respond. When I repeatedly pressed F5 for debugging, it would say that debugging already exists.

@LongQIByte LongQIByte added the bug Something isn't working label Mar 20, 2019
@LongQIByte
Copy link
Author

I added the cuda environment to the original Docker base. I don't know if it is affected by this, but I will also have this effect by running the docker run command in the readme.
The docker I made is public. The command is: docker pull registry.cn-hangzhou.aliyuncs.com/test_tzf/test:0.1.4

@kylecarbs
Copy link
Member

kylecarbs commented Mar 20, 2019

There are still some issues with debugging from the docker container that we'll need to fix. Looking into this now.

Update: Found the issue. Will push a new release shortly.

@MichaelDesantis
Copy link
Contributor

Possible duplicate of #210 ?

@kylecarbs kylecarbs self-assigned this Mar 26, 2019
@kylecarbs kylecarbs added this to the March 2019 milestone Mar 26, 2019
@kylecarbs
Copy link
Member

Fixed with the latest release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants