Josef Procházka

> Also the `runtime.timeoutAt` doesn't work for standby runs, because the timeout is dynamic there based on incoming and in-flight requests.. What value does it actually have in such case?

This is now fully implemented in Python version of the `crawlee` and it has to be migrated to the JS version. For reference, see the linked issues mentioned in this...

Maybe we should rather allow passing custom http client to the `ApifyClientAsync`, `ApifyClient` init methods? What do you think @janbuchar , @vdusek ?

Hello, @cmosguy we had internal discussion about this and agreed to allow passing a custom http client to `ApifyClientAsync`, `ApifyClient` init methods, which will allow you to pass your specifically...

Caused by bump of python-certifi from 2025.1.31 to certifi 2025.4.26 https://github.com/certifi/python-certifi/issues/349 Let's pin python-certifi to 2025.1.31 for now and wait for the upstream issue to be fully resolved.

Close this after the upstream issue is resolved and `certifi` can be removed from the dependencies again

It seems ok according to mypy like this and unit tests are passing as well, but I am not really sure about this though. As discussed here: https://github.com/apify/crawlee-python/pull/1086/files/a67d3b3b42d2a1d59923810fe6f17dabeea3e98b#r1995086090 there are...

This issue is caused by a misaligned CLI and the storage client. Re-opening with a potential fix prepared

Should be solved by https://github.com/apify/apify-sdk-python/pull/677

Previously, when users wanted to create their own headers, they could do something like this: ``` apify_client = ApifyClient(...) apify_client.http_client.httpx_client.headers.update(custom_headers) ``` After changing to `impit`, this no longer seems possible....