Zanie Blue

Great thanks! That's really helpful. The primary issue here is that there's multithreaded access to the task runner but an `asyncio.Event` is not thread-safe. We require multithreaded access to the...

The implementation of deterministic sorting of JSON for serialized flows in v1 may be useful for this.

Hi! Generally v1 UI issues should be opened at PrefectHQ/ui, but this is actually an API limit. We enforce timeouts on queries to avoid slowdowns for other users. It looks...

You can use `aggregate` calls e.g. ```graphql { flow_run_aggregate( where: {start_time: {_gt: "2022-08-03T10:24:25.062468+00:00"}} ) { aggregate { count } } } ``` I'd recommend scoping your log queries to a...

Hi! Thank you for reporting this issue. I believe this is because the UI displays is displaying state types for this selector. States have both "names" and "types". Types are...

Regarding manual retrieval from storage -- we could just always add the timestamp to bring this in line with other storage methods e.g. `flow-name-{timestamp}.prefect` then since it's a local file...

Hey @fjord-prefect -- I think this will mostly be resolved by planned improvements to our caching interface. Basically, the upstream tasks that you don't want to re-run will be easily...

I'd be willing to review a community contribution of this but I am not sure it belongs in this repository and we will likely not be able to prioritize such...

The implementation is actually quite short, see https://github.com/celery/celery/blob/master/celery/contrib/sphinx.py

Interesting. As noted, we include this for flows so we can JSON parameters from the API but task runs do not track their parameters this way as they are always...