Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
bioinformatics-computational-biology
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
shameless-promotion
linkedin-flyte
random
deployment
hacktoberfest-2023
flyte-github
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#torch-elastic
Title
# torch-elastic
f
Fabio Grätz
06/19/2023, 7:25 AM
https://github.com/flyteorg/flytekit/pull/1677
Need feedback on this fix, thx 🙂 Maybe
@Kevin Su
@Niels Bantilan
@Eduardo Apolinario (eapolinario)
? Doesn’t have time pressure
n
Niels Bantilan
06/20/2023, 1:53 PM
LGTM, will defer to others regarding the “local” execution id issue
f
Fabio Grätz
06/20/2023, 2:39 PM
Thanks for taking a look!
2 Views
Post