Hey folks my teammates and I are trying to migrate a monorep

Question

Hey folks my teammates and I are trying to migrate a monorepo of tasks amp flows from Prefect 1 to Prefect 2 As part of that we re naturally doing some testing We were previously using the `is successful ` method in an assert in our testing and to move that to Prefect 2 we were thinking we might call `get run context ` to get the flow run state and return some value likely Completed from the `state name` parameter We ve observed that calling `get run context ` within a flow s context causes the flow to hang Has anyone observed this or does anyone have any suggestions for remedy

Zanie · Answer

That s really weird Calling `get run context` should never hang If you share a MRE that d be helpful

Zanie · Answer

That said you shouldn t need to access the run context for testing what are you trying to do

Kevin McCraney · Answer

thanks for your response < Zanie> If you let me know what MRE stands for I would be happy to share one

Zanie · Answer

Minimal reproducible example slightly smiling face

Kevin McCraney · Answer

thanks much

Kevin McCraney · Answer

I figured out a way around what I wanted to do but it does raise another question about flow name behavior I have a named flow that I am spinning up in pytest When I run my collection of tests I get a warning that says ```UserWarning A flow named double quote cleanup flow and defined at XXX location conflicts with another flow Consider specifying a unique `name` parameter in the flow definition ` flow name= my unique name ` warnings warn Docs <https docs pytest org en stable how to capture warnings html>``` I ve added a uuid to the flow name so it s different every runtime and that suppresses the error Is there a suggested way of deregistering flows if they re called in a test suite

Zanie · Answer

Yeah we reset the registry after every test internally It s in our conftest file I can link when I m back at my laptop

Kevin McCraney · Answer

no worries michael thanks smile

Zanie · Answer