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

python services do not work with skaffold debug, cause status check failure. #500

Closed
j-windsor opened this issue Jun 9, 2021 · 0 comments · Fixed by #501
Closed

python services do not work with skaffold debug, cause status check failure. #500

j-windsor opened this issue Jun 9, 2021 · 0 comments · Fixed by #501
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@j-windsor
Copy link
Contributor

  • Since uwsgi is a binary and not pure python, the skaffold python debugger is unable to detect python sessions to debug. This case applies to all flask services in this sample. Running skaffold debug will result in error launching python debugging: unable to determine python version from \"uwsgi\".
  • The same reasoning applies to bash script files. When a bash script is called as the entrypoint that in turn calls python code, running skaffold debug will result in error launching python debugging: unable to determine python version from \"/bin/bash\". This applies to the loadgenerator service in this sample,
@NimJay NimJay added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p3 Desirable enhancement or fix. May not be included in next release. labels Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants