Chris Guidry
Chris Guidry
> Should the agent follow the same naming scheme as orion? @hallenmaia I know this may seem weird to be inconsistent, but I actually think it should still be called...
I've been investigating this memory leak and one issue I've found with the parameter case is that after garbage collection, the chain of referrers looks like: * the task parameters...
For a task that returns a large value, it's also the `Call`, but this time it's the `Call.future` that's holding a long-term reference to the result of the call. It's...
In the case of task return values, at the end of a flow run there are three references: 1: a `Call` object's `.future`
Hi @sibbiii, I just merged a fix that will be in the next release, but if you could give it a try on `prefect@main`, that would be amazing! I was...
Ah yes, @sibbiii, that is likely to still be the case during the flow run. My fix corrected an issue where memory wasn't freed _between_ flow runs, but it wouldn't...
We've been discussing internally how we may need to take a fresh look at how results are handled across the board, with memory efficiency in mind. Thanks for your help...
Hi Yaron, are you using a Prefect Cloud push work pool? If not, I don't think we can help you with the Docker rate limit, that's something you'd need to...
Ah I'm sorry, I meant a fully managed work pool (one where Prefect Cloud runs the actual workloads too). So in this case, Prefect Cloud is still sending the work...
Actually, I'm going to re-open this to remove the comment and make it a `>=`