SDK 2 finalization

[B4nan]

• availableMemoryRatio not used at all, should be used in snapshotter
  • feat: Memory usage limit configuration via environment variables crawlee-python#502
• memoryMbytes not used at all, should be used in snapshotter
  • feat: Memory usage limit configuration via environment variables crawlee-python#502
• separate apify deployment guide as in https://crawlee.dev/docs/deployment/apify-platform
  • docs: Deployment guide crawlee-python#482
• apify client batch add requests not handled properly (API allows only 25 items in one call)
  • ApifyRequestQueueClient.batch_add_requests cannot handle more than 25 requests apify-client-python#264
  • fix: Hotfix for batch_add_requests batch size limit #261
• actor templates with crawlee for python
• logging configuration in SDK
• more python playwright images (later)

[B4nan]

also maybe the disableBrowserSandbox flag which adds --no-sandbox to chrome launch args, which was needed for playwright on platform IIRC

[janbuchar]

also maybe the disableBrowserSandbox flag which adds --no-sandbox to chrome launch args, which was needed for playwright on platform IIRC

This might be worth digging into - I couldn't find any documentation of the variable. I'm pretty sure playwright works just fine on platform without that.

[B4nan]

Maybe, I just tried to find when we added it and it is really ancient, here is a commit that apparently reverts its removal:

apify/apify-ts@c4a44af

Also some relevant SO post:

https://stackoverflow.com/questions/50662388/running-headless-chrome-puppeteer-with-no-sandbox

Maybe it's not relevant anymore, and maybe its just about chrome and not chromium (looking at our python playwright docker image, we don't use chrome in there, right?)

[janbuchar]

Maybe it's not relevant anymore, and maybe its just about chrome and not chromium (looking at our python playwright docker image, we don't use chrome in there, right?)

Yeah, looks like we only allow chromium, on the type level. If you install chrome and ignore the type error, it will probably work though.

[B4nan]

we'll need to try it, should be enough to run pw+chrome with js version with disableBrowserSandbox: false on platform, same for puppeteer i guess, but i can imagine both will behave the same. i would also try both headless/headful modes.

[vdusek]

Seems to be ready, closing, and releasing 2.0.