I'm getting "Skipped (metadata unchanged)" upon registering a flow that I've updated (as in, the sou...

Philip MacMenamin

08/03/2021, 4:51 PM

I'm getting "Skipped (metadata unchanged)" upon registering a flow that I've updated (as in, the source code has changed, and is being ignored.

Philip MacMenamin

08/03/2021, 4:52 PM

prefect register --project proj_name -p /path/flow.py -n mesh_to_glb

Zanie

08/03/2021, 4:52 PM

Hey @Philip MacMenamin -- if the structure of the flow doesn't change, there is no change in the metadata that is sent to Cloud so it is 'skipped'

Kevin Kho

08/03/2021, 4:53 PM

Hey @Philip MacMenamin, added to Michael’s comments, if you change the executor from LocalExecutor to DaskExecutor, that is not saved in the metadata also.

Philip MacMenamin

08/03/2021, 4:55 PM

I'm running the flow on a server hosted by me (locally) - this is considered "Cloud" ?

Kevin Kho

08/03/2021, 4:56 PM

For this purpose they would behave the same yep.

Philip MacMenamin

08/03/2021, 4:56 PM

I'm addling logging.info within tasks, and I'm not seeing these logging events, the version remains at 1

Philip MacMenamin

08/03/2021, 4:56 PM

this is expected behaviour?

Philip MacMenamin

08/03/2021, 4:58 PM

well, actually more than that, I've changed functionality of the source. I guess I don't understand why this is considered to not have changed.

Kevin Kho

08/03/2021, 5:00 PM

It’s about the change in

flow.serialized_hash

so if you add code to the task, it doesn’t affect the serialized hash because Prefect only stores the metadata , and not the actual code. You can force registration though with:

prefect register --force ...

Philip MacMenamin

08/03/2021, 5:06 PM

ok -

Copy code

--force

did the trick -thanks!

👍 1

2 Views

Open in Slack

Previous Next

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.