David Manouchehri

> This could certainly be an option to resolve our CI issue, thanks for bringing it to our attention. In _theory_ you can also run Linux natively on the M1,...

Ran into a similar issue (no aarch64 support in our automated GitHub Action pipeline) with an unrelated product that my team is working on, but thought you might find this...

@mvanotti Are you still running into this?

Any update on this?

@hmakholm I deleted my comment earlier after figuring out it was unrelated myself, but thank you for providing a solution anyway! =D

@s3rvac Do your servers at work have 128 GB of RAM? I'm wondering if this is a larger design issue; formerly an analyst would be using RetDec on a remote...

```yaml litellm_settings: drop_params: True cache: True cache_params: type: s3 s3_bucket_name: os.environ/CACHING_S3_BUCKET_NAME s3_region_name: os.environ/CACHING_AWS_DEFAULT_REGION s3_aws_access_key_id: os.environ/CACHING_AWS_ACCESS_KEY_ID s3_aws_secret_access_key: os.environ/CACHING_AWS_SECRET_ACCESS_KEY s3_endpoint_url: os.environ/CACHING_AWS_ENDPOINT_URL_S3 failure_callback: ["sentry", "langfuse"] num_retries_per_request: 3 success_callback: ["langfuse", "s3"] s3_callback_params: s3_bucket_name: os.environ/LOGGING_S3_BUCKET_NAME...

Heading to bed atm, will do tomorrow! Thank you! This one and the s3 team logging are the two highest priorities for me for sure. Do you want me to...

This is still a bug btw, checked today.

Reopening as it doesn't seem to actually work when running LiteLLM as a proxy server.