urimandujano

@desertaxle can I get your thoughts on this? The bug in this case happens when our flow-run has an `infrastructure_pid` but the `configuration` object isn't found. I think it makes...

I'm going to go ahead and mark this as ready for review since I'm pretty sure it'll prevent the specific case the user was running into (a worker swamped with...

Hey @yaronlevi - it looks like that flow run was deleted by an automation and after a flow-runs gets deleted, any attempts to visit in the UI will result in...

Let me follow up with more details via DM.

Thank you for the suggestion! The proper import statement would be: ```python from prefect.flow_runs import wait_for_flow_run ``` We'll get this detail added to the docs.

Hey @kzeitz, I think you've found a gap in our pydantic v2 support logic. Based on your comment and original bug report, it looks like the issue is specifically when...

hey @ohadch - thank you for taking the time to come up with this implementation (which looks solid). I've just started working on this feature internally and I think it...

I think this can be accomplished when you're building the deployment -- either by building a custom image that contains the flows' dependencies or by providing extra configuration to install...

I think this is related to https://github.com/pydantic/pydantic/pull/6681 which was fixed in pydantic v2. I'm linking this to our ticket for updating to pydantic v2 since I expect this issue will...