do we already have a workaround or fix for this? <...
# flytekit
j
do we already have a workaround or fix for this? https://github.com/flyteorg/flyte/issues/2508
k
cc @jeev can you push a PR?
j
@Ketan (kumare3): curious if the change make sense, or should this be handled on flyteadmin's side.
we are slightly behind on our versions, so it may already have been fixed
@Vrinda Vasavada: would be useful to list our versions in the issue as well
👍 1
y
i think this makes sense… thank you for finding it. mind putting in the PR?
v
yeah I can put the PR out! we're on flytekit
0.30.3
and flyteidl
0.22.3
(will add these to the issue too)
k
hmm we are on 1.0.2 now
v
yeahhh we need to upgrade all of our projects but are a bit behind! I'll put out the PR and will link the other possible location for this fix on the flyteadmin side
j
yea we’re working on the upgrade across the org.
would be good to confirm if this is still an issue in 1.0.2. maybe we can try to repro against the latest flyte @Vrinda Vasavada ?
v
yeah agreed! i'll try upgrading our sandbox and see if I can reproduce this
okay, still the same issue with
flytekit==1.0.2
and
flyteidl==1.0.1
@Eduardo Apolinario (eapolinario) thanks for approving and merging it in! would it be possible to release a patched version of
0.26.1
with this fix in the meantime while we work on upgrading to
1.0.2
?
e
@Vrinda Vasavada, I just released 0.26.2. Can you give it a try and let us know if it solved the issue for you?
v
thanks a bunch! will try it out!
that fixed it, thank you @Eduardo Apolinario (eapolinario)!
e
Amazing. Thank you for the fix, @Vrinda Vasavada!
❤️ 1
130 Views