is this a known issue? happens when upgrading to f...
# flyte-console
f
is this a known issue? happens when upgrading to flytekit 1.0 and using launchplans
t
i remember this happening @late-eye-50215 briefly but don’t remember the resolution. i definitely don’t see it anymore.
@famous-businessperson-24711 can you tell us which version admin/propeller are on?
release-1.0.0
?
and what did you mean by using launch plans? was this execution kicked off from a launch plan in another workflow?
f
launchplans as opposed to subworkflows
t
and console version actually
f
😬 i'll pass that to @colossal-solstice-11091 or @swift-animal-75798
s
f
Copy code
flytekit==1.1.0b6
t
trying these versions locally
wait no.. sorry i was wrong
i am still seeing this
f
any status update on this? makes most of the UI components not work 🙂
t
@late-eye-50215
l
@plain-magazine-78373
Hey @famous-businessperson-24711 we’re having some trouble repoing this behavior - question: which version of console are you running?
(Oh never mind - 1.1.1)
Is there anything unusual about this launch plan?
t
i can repro this
p
@thankful-minister-83577 can you send me a link to a plan please?
t
f
It says subworkflows but the confusing thing is that they're launch plans
p
Hey Dylan, I've taken a look into it, and found where the culprit of this issue occurs - I'm gonna continue working on it tomorrow and will update you on the timeline on getting this thing solved!
f
Thank you 🙏
p
hey Dylan! We've just merged the fix for this issue, so you can either check it out on the latest master or wait till the next 'console' release. Let us know if you still experience this problem after the fix!
f
so it's a console issue not a flytekit one?
p
correct
f
cool thanks, i'll just wait for the next rollout then 🙂 attn: @swift-animal-75798 @colossal-solstice-11091
👍 2