Hi, I’ve found a bug with the master flyte repo. N...
# ask-the-community
g
Hi, I’ve found a bug with the master flyte repo. Not sure if this is the expected behavior 1. Execute a task with caching enabled. 2. Next time, use
--overwrite-cache
for wf execution, to get new cached entry. 3. Execute another task that will be cached. because of step 2 4.
view source execution
for the cached task redirects to task execution of step 1. I believe it should redirect to latest task execution in step 2.
j
how are you executing the 3rd step? is it separately executed from 2nd step or is it part of the workflow
g
Sorry, in 3rd step, I mean execute another workflow
In the wf executed in step 3, the mentioned task will be cached with values in step 2. I hope it's clear
j
i see, so this is going on then • WF1 runs following ◦ task1 ▪︎ cache1 is saved ◦ task2 • task1 runs with
--overwrite-cache
◦ cache2 is saved • WF1 runs again ◦ task1 uses cache but uses cache1 not cache2 does it look correct?
g
No. It’s like below. • WF ◦ Run 1 ▪︎ Task 1 --> cache 1 ◦ Run 2 ▪︎ Task 1 (cache 1) ◦ Run 3
--overwrite-cache
▪︎ Task 1 --> cache 2 ◦ Run 4 ▪︎ Task 1 (cache 2) ▪︎ However, if I click on the
view source execution
, it takes me to
Run 1
. It should take me to
Run 3
Note that I’m talking about this button
j
i see, yeah i think that is a bug 🤔 you can file an issue with the min reproducible code
s
[flyte-bug]