mega mega mega Hi Flyte community Join us tomorrow for the b

Question

mega mega mega Hi Flyte community Join us tomorrow for the bi weekly Community meeting including book New community contributed content dart New Governance model proposed zap kubernetes Lighting Talk K8s Ingress why what and how page facing up New Getting Started guide bulb Guest presentation by < Sören Brunk> on how USU AI Services uses Flyte for production and experimental setups clock1 Tuesday Feb 21 at 9am PT rotating light According to community feedback we re going back to Zoom calendar Subscribe to the calendar import it to your calendar app

Greg Gydush · Answer

Was this recorded by chance

David Espejo (he/him) · Answer

< Greg Gydush> it was we ll let you all know once recordings are up in YouTube Anything particular in the agenda caught your attention

Greg Gydush · Answer

Thank you I heard that debugpy was mentioned for debugging Flyte workflows and it s also fun to hear other updates

David Espejo (he/him) · Answer

Right It s mentioned in a recent blog post by < Fabio Grätz> During the meeting Fabio shared more details Hope you can catch the recording

Greg Gydush · Answer

yep I tried it myself after reading the blog and it worked great

Fabio Grätz · Answer

Happy to hear slightly smiling face

Greg Gydush · Answer

Thanks for sharing that

Dan Corbiani · Answer

This is pretty slick

Greg Gydush · Answer

< Fabio Grätz> 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

Greg Gydush · Answer

Trying to get a solid user experience as this is mostly for ML scientists bioinformaticians debugging remote workflow executions

Fabio Grätz · Answer

I do `kubectl port forward pod lt pod name gt `

Fabio Grätz · Answer

Works well

Greg Gydush · Answer

Yep that s my move as well

David Espejo (he/him) · Answer

Highlights of this week s meeting Community updates Logistics update 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 book film projector film projector Presentation arrow right We hope to see you in the next one

Greg Gydush · Answer

< Fabio Grätz> < Ketan kumare3 > 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 ```python m debugpy listen 0 0 0 0 5678 lt task workflow gt ```

Greg Gydush · Answer

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

Greg Gydush · Answer

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

Ketan (kumare3) · Answer

But you need to pause the process

Ketan (kumare3) · Answer

Granted pyflyte execute can pause when enabled

Greg Gydush · Answer

What do you mean by that The breakpoint in the gutter pauses the process after connecting

Greg Gydush · Answer

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

Ketan (kumare3) · Answer

But after connecting

Greg Gydush · Answer

yep

Ketan (kumare3) · Answer

But the task has to start a debug server and wait for connecting right

Greg Gydush · Answer

It would

Greg Gydush · Answer

Both are potentially possible