Ondra Urban

No, sorry. But it's not dead, we're just completely reworking the way this and many other things will be handled. For reference see [the Actor specs](https://github.com/apify/actor-specs)

AFAIK Apify packages are usually installed with `npm install` whereas you use `npm ci`. It might be the cause of your issues. Have you tried the [recommended Dockerfiles](https://sdk.apify.com/docs/guides/docker-images)?

We're running hundreds of thousands of runs and thousands of builds on those images every day, they're not broken per se. But they might be broken in some specific configurations....

Thanks for sharing @kejiweixun. That's interesting. Are you using a lock file?

I don't think this is a bug really. It's quite obvious that strings of unlimited sizes cannot be loaded or parsed. That's why the list functions of client have offsets...

I think it might be because of the keepalive connections and HTTPS tunneling. How does the client learn that the pod is down and it should retry elsewhere?

Still relevant in client v1 ``` TypeError [ERR_UNESCAPED_CHARACTERS]: Request path contains unescaped characters at new NodeError (node:internal/errors:329:5) at new ClientRequest (node:_http_client:164:13) at Object.request (node:https:333:10) ```

Wouldn't an iterator that works in batches be preferable instead of streams? Two reasons: First is that processing each item as an event is not effective and there's a lot...

Hmm, interesting. `events` is a Node.js only module, so it makes sense that it's not available in React Native. Interestingly, we've been using `apify-client` in the browser for quite some...

Yeah, should be. It won't work in the browser, but we can live with that.