https://flyte.org logo
Join Slack
Powered by
:mega: :mega: :mega: Hi Flyte community! Join us ...
# announcements
a
📣 📣 📣 Hi Flyte community! Join us tomorrow for the bi-weekly Community meeting, including: • 📖 New community-contributed content • 🎯 New Governance model proposed • ⚡kubernetes Lighting Talk: K8s Ingress: why?, what? and how? • 📄 New Getting Started guide • 💡*Guest presentation by @boundless-pizza-95864 on how USU AI Services uses Flyte for production and experimental setups* 🕐 Tuesday Feb 21 at 9am PT 🚨 According to community feedback, we're going back to Zoom: join here 📆 Subscribe to the calendar (import it to your calendar app): Flyte calendar ICS file
❤️ 5
flyte 5
💯 5
🔥 6
r
Was this recorded by chance?
a
@rich-garden-69988 it was! we'll let you all know once recordings are up in YouTube. Anything particular in the agenda caught your attention?
r
Thank you! I heard that debugpy was mentioned for debugging Flyte workflows and it's also fun to hear other updates!
a
Right! It's mentioned in a recent blog post by @cool-lifeguard-49380 : https://medium.com/@fabiograetz/attach-a-visual-debugger-to-ml-training-jobs-on-kubernetes-eb9678389f1f During the meeting, Fabio shared more details. Hope you can catch the recording!
r
yep! I tried it myself after reading the blog and it worked great!
🙌🏽 1
🙌 2
c
Happy to hear 🙂
r
Thanks for sharing that!
🙂 1
c
This is pretty slick
🔥 1
r
@cool-lifeguard-49380 did you get this working well with pod selector? Going by pod IP is less convenient, so I’ve opted to just port forward with kubectl for now, and use local host IP, if that makes sense
Trying to get a solid user experience, as this is mostly for ML scientists/bioinformaticians debugging remote workflow executions
c
I do 
kubectl port-forward pod/<pod name>
Works well
r
Yep, that’s my move as well
👍 1
a
Highlights of this week's meeting: • Community updates ◦ Logistics update: agenda doc is now open including attendance list and voluntary note taker for each session ◦ Blog posts authored by Dr Fabio Graetz and Bernhard Stadlbauer • Soeren Brunk presentation and further discussion 📖 Read the notes 📽️

Community Updates▾

📽️ Presentation:

"The right GPU in Flyte for you"▾

➡️ Subscribe to the calendar We hope to see you in the next one!
❤️ 6
🦜 7
🔥 12
flyte 3
r
@cool-lifeguard-49380 @freezing-airport-6809 Could we possibly do this without any modifications to the workflow (notably the debugpy statement, which requires a re-register) by adding this as a task/workflow override? I’m imagining something like, before running pyflyte run from within the container, we would run
Copy code
python -m debugpy --listen 0.0.0.0:5678" <task/workflow>
Then we could add a debug boolean field to the UI, and the process would look like, run workflow on remote, place breakpoint on local Vscode, run debugger (which connects to remote process)
This shows that you can set breakpoints in the gutter (no need for explicit breakpoint() call) - so as long as we can listen, we can attach!
f
But you need to pause the process
Granted, pyflyte execute can pause when enabled
r
What do you mean by that? The breakpoint in the gutter pauses the process after connecting
so if you had this on the task, and the first line was a breakpoint, it would pause at the breakpoint (provided you’ve connected the debugpy debugger)
f
But after connecting
r
yep
f
But the task has to start a debug server and wait for connecting right
r
It would
Both are potentially possible?
158 Views
Open in Slack
PreviousNext
Powered by