-
Notifications
You must be signed in to change notification settings - Fork 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
Fix Flyin Plugin VSCode download bug #1991
Fix Flyin Plugin VSCode download bug #1991
Conversation
Signed-off-by: Future Outlier <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1991 +/- ##
==========================================
+ Coverage 85.73% 85.74% +0.01%
==========================================
Files 313 313
Lines 23455 23492 +37
Branches 3516 3516
==========================================
+ Hits 20109 20144 +35
- Misses 2737 2738 +1
- Partials 609 610 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Future Outlier <[email protected]>
plugins/flytekit-flyin/setup.py
Outdated
@@ -15,7 +15,7 @@ | |||
author_email="[email protected]", | |||
description="This package holds the flyin plugins for flytekit", | |||
namespace_packages=["flytekitplugins"], | |||
packages=[f"flytekitplugins.{PLUGIN_NAME}"], | |||
packages=[f"flytekitplugins.{PLUGIN_NAME}", f"flytekitplugins.{PLUGIN_NAME}.vscode_lib"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now that we have more than one package in this plugin, can we use setuptools find_packages instead of listing them exhaustively here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I can try it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update: I will do this in a new PR.
…nto flyin-code-server-extension_paths-bug-fix Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
…nto flyin-code-server-extension_paths-bug-fix Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
…yin-code-server-extension_paths-bug-fix
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Signed-off-by: Future Outlier <[email protected]>
Tracking issue
Fixes flyteorg/flyte#4284
Why are the changes needed?
We don't support cases when using default flyin image and we want to install additional extensions.
https://github.com/flyteorg/flytekit/blob/master/plugins/flytekit-flyin/Dockerfile
For example, you use
COPILOT_CONFIG
, which include python, jupyter and copilot extensions in the list.The old code will not install the copilot extensions for 2 reasons:
decorator.py
, which will skip downloading additional extensions ifcode-server
is executable in the beginningHow was this patch tested?
unit test and in single binary mode.
Setup process
docker buildx build --platform=linux/amd64 -t localhost:30000/flyin-0112:1536 -f DockerfileFlyin_v2 . docker push localhost:30000/flyin-0112:1536 pyflyte run --remote --image localhost:30000/flyin-0112:1536 vscode_task.py wf
Screenshots
code-server --list-extensions
Test Screenshot
Check all the applicable boxes
Related PRs
Docs link