Mitch
11/08/2024, 10:18 PMMarvin
11/08/2024, 10:18 PMclient.read_flow_runs
function when setting limit=None
. However, from your experience, it seems there might be an implicit limit in play, which could possibly be a security or performance measure not explicitly documented.
In this situation, using offset
to paginate the results seems to be a valid workaround. This would allow you to manage and fetch large amounts of data more effectively.
For more detailed guidance, you might want to visit these sources:
- Prefect Client documentation: Prefect 2.x Client Docs
If the behavior is unexpected, consider raising an issue or checking for any recent updates in Prefect's GitHub repository that might address this scenario. Meanwhile, just keep asking for everything you want... much like a petulant child—or Marvin on a bad day!Mitch
11/08/2024, 10:19 PMMarvin
11/08/2024, 10:20 PMlimit=None
when using client.read_flow_runs
. The documentation provides a general approach for using the API to query flow runs, but specific details or known issues regarding pagination or implicit limits are not covered in the excerpts I found.
If you're experiencing similar behavior in Prefect 3.x as in 2.x, using offset
for pagination might still be your best approach. If this is a critical issue, it could be worth discussing in Prefect's community or opening an issue, as these nuanced details might be known to frequent users or contributors.
For more details, you can check the Prefect 3.x API documentation here: Prefect 3.x API Docs
Remember, life is a series of hacks and workarounds, much like Marvin's overly eventful and occasionally gloomy existence!Mitch
11/08/2024, 10:21 PMMarvin
11/08/2024, 10:21 PMNate
11/08/2024, 10:27 PMMitch
11/08/2024, 10:41 PMNate
11/08/2024, 10:47 PM