Judson Stephenson

Also happening to me. I can confirm setting `useHostResolver: false` fixed the issue for me as well. Same configuration, 2021 M1 Mac Pro, 16GB.

@rnicholus if you are provisioning server keys via IAM instance profiles (AWS best practices), you must supply the `sessionToken`, which is currently not possible with fine-uploader (while using backend signing)

@rnicholus If there was a way to pass through the `x-amz-security-token` header from the signature response, and have fine-uploader use it when communicating with S3, that would work.

@blakewatters Fixed that comparison. Wasn't really using my brain on that one.

Just ran into this as well. The SNS unsubscribe permission is the only one that can't be tailored to a narrow IAM role.

I'm for this change :+1: . After adding in `HasManyThrough` (https://github.com/judsonco/pheasant/commit/acc46036b2fd4875f9807659b96876d2b590c2ea) relationships and `HasOneThrough` (https://github.com/judsonco/pheasant/commit/3e0c82b8119b1d2776cfc7ae6094347f7dacede2) there's lots of hackiness around getting the current table alias and it seems like DBAL...

@bjornpost re: the docs, they are relatively unchanged. IMO this just makes the existing transaction code work like a casual observer would expect them to. I'll open another issue for...

As a test, I performed the following with the workers as outlined above: ``` ruby 20.times do $rewquest_workflow_client.start_execution(b) end ``` With the forking workers, there are many activities that are...

@mjsteger this error could be a red herring -- I _do_ get this error with `:use_forking => false` as well. Though, it will be nice to clean up that error...

@mjsteger after more testing, with `:use_forking => false` I can replicate the behavior where the activity worker accepts a task, but fails to execute, resulting in a timeout. 1) Start...