JackKelly-Bellroy

This may not be possible right now, but I wanted to log information that I found. At time of writing, `hal` does not report a call stack on lambda errors:...

Append `install_options`?

2

It appears that flags specified with `install_options` are prepended to the argument list that gets passed to the installer: https://github.com/cachix/install-nix-action/blob/master/lib/install-nix.sh#L32 This means that the hardcoded `--daemon` will override any `--no-daemon`...

shellFor: creates duplicate `buildInputs` on large projects, exceeding argument length limits

2

I work on a medium-sized haskell monorepo (~40KLOC spread over 30 packages), and discovered that adding a dependency that already existed caused `nix-shell` and `nix develop -f .` to begin...

aarch64-darwin: Passing `system = "x86_64-darwin"` still triggers build of aarch64 GHC

12

We tried to use `haskell.nix` on an M1 Mac with Rosetta 2 installed, by overriding the `system` parameter: ```nix let # NB: We are _not_ using flakes here pkgs =...

Custom schedules

2

Add two parameters to the CFN stack: * `CleanSchedule` lets the frequency change, but keeps the default at `rate(1 hour)` to maintain existing behaviour * `LogRetentionInDays` stops the logs from...

Rename `actions/foo` to `actions.foo`?

2

There are an increasing number of record keys of the form `actions/foo`. This gives a quasi-namespacing effect but maybe we want to push them into a separate record, since AFAIK...

With `Runtime: provided`, `sam build` copies source to a temp dir, breaking builds that use relative paths

3

**Description:** When `sam build` tries to build a `runtime: provided` `Function`, if the build system uses relative paths then it will fail when copied to the temporary directory `sam build`...

dhall: raise upper bound on Diff

2

We have set `allow-newer` internally and it is working.

Structures for not-just-lambda events?

2

At work, we're considering using [Lambda Destinations](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations) to respond to failed asynchronous lambda invocations. The obvious thing to do would be to PR some new types and `ToJSON`/`FromJSON` instances for...

Force response body update

1

Fixes #538 Draft for now, but keen for comments: do you prefer strict `let`s? `seq`? Bang patterns? We will test this internally before recommending that it gets merged.