Adam Dobrawy

@Brooke-white the use of profiles that must be saved to disk as a file is not an effective solution to the issue. This interferes with multi-threaded access to multiple AWS...

Is there anything what I can do to make that change happen?

If anyone interested that change can be easily tested eg. via: ``` - repo: https://github.com/gruntwork-io/pre-commit rev: 837cfa83f27ec2dd4a4c6860b2a6ca9392642fe0 hooks: - id: terraform-fmt - id: terraform-validate exclude: terragrunt/modules ```

@der-joel in Django to have it workings it's enough in configuration to have: ``` CELERY_BROKER_TRANSPORT_OPTIONS = { "queue_order_strategy": "priority", "priority_steps": list(range(10)), } CELERY_TASK_INHERIT_PARENT_PRIORITY = True ``` The exception you have...

@kleschenko could you rebase? Looks like a lot move forward around pyarrow, so it's worth trying out what new blockers we have here.

One more workaround... AWS EKS AMI provides RSS about new releases: https://github.com/awslabs/amazon-eks-ami/releases.atom You can subscribe RSS feed eg. in Slack: https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack

Thanks for making it clear!

Hello, I work for Select Star. When it comes to integration testing, we are happy to provide a free environment so you can monitor the connector to ensure it is...

> sorry for mistakenly approving. the tests are failing and we still need design decision confirmed. Thanks for raising the issue of tests. I will take look into that next...

> Can't we handle this with existing model fields? what additional benefits this change will provide? In order for the example to work properly without changing code it is required...