do we already have a workaround or fix for this

Question

do we already have a workaround or fix for this <https github com flyteorg flyte issues 2508>

Ketan (kumare3) · Answer

cc < jeev> can you push a PR

jeev · Answer

< Ketan kumare3 > curious if the change make sense or should this be handled on flyteadmin s side

jeev · Answer

we are slightly behind on our versions so it may already have been fixed

jeev · Answer

< Vrinda Vasavada> would be useful to list our versions in the issue as well

Yee · Answer

i think this makes sense thank you for finding it mind putting in the PR

Vrinda Vasavada · Answer

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

Ketan (kumare3) · Answer

hmm we are on 1 0 2 now

Vrinda Vasavada · Answer

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

jeev · Answer

yea we re working on the upgrade across the org

jeev · Answer

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>

Vrinda Vasavada · Answer

yeah agreed i ll try upgrading our sandbox and see if I can reproduce this

Vrinda Vasavada · Answer

okay still the same issue with `flytekit==1 0 2` and `flyteidl==1 0 1`

Vrinda Vasavada · Answer

< 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`

Eduardo Apolinario (eapolinario) · Answer

< Vrinda Vasavada> I just released Can you give it a try and let us know if it solved the issue for you

Vrinda Vasavada · Answer

thanks a bunch will try it out

Vrinda Vasavada · Answer

that fixed it thank you < Eduardo Apolinario eapolinario >

Eduardo Apolinario (eapolinario) · Answer

Amazing Thank you for the fix < Vrinda Vasavada>