Robert
Robert
With the way the library determines types, I believe the following works: ``` type uuid string vars := map[string]interface{}{ "id": uuid("my-id"), } ``` (`uuid` here should be literally the type...
The problem was: ``` error: infinite recursion encountered at /nix/store/46v5hkwaa7aadrdn3gadlcx8ckrv3brj-source/pkgs/stdenv/generic/make-derivation.nix:311:7: 310| depsBuildBuild = lib.elemAt (lib.elemAt dependencies 0) 0; 311| nativeBuildInputs = lib.elemAt (lib.elemAt dependencies 0) 1; | ^ 312| depsBuildTarget...
The static build failed after 5h with ``` 2022-09-20T17:15:52.1934543Z Linking dist/build/hackage2nix/hackage2nix ... 2022-09-20T17:15:54.0546032Z /nix/store/z86a6y1k0r6d5fh9sqxbc1g58bhz8fwq-binutils-2.38/bin/ld: cannot find -lcrypto: No such file or directory 2022-09-20T17:15:54.1512793Z collect2: error: ld returned 1 exit status...
A wild stab at a fix for the hackage2nix `-lcrypto` error: In nixpkgs commit [2a49c87bc5365ebbaad4cc3eebdec78b2474cf6e](https://github.com/NixOS/nixpkgs/commit/2a49c87bc5365ebbaad4cc3eebdec78b2474cf6e), hopenssl was changed to depend on `openssl_1_1` instead of `openssl`. So https://github.com/PostgREST/postgrest/pull/2479/commits/b8a3be80a9e683e4351f2ff509ec5a4b7e9e8ed2 patches static-haskell-nix to...
I think my latest changes might have fixed the build, but it seems it's being timed out after 360 minutes... Not sure what to do about this. Could we try...
> > We'd have less pressure to upstream patches to dependencies, resulting in less incentive to make high-quality changes, and less incentive to be good contributors to the general Haskell...
I've done a bit of digging into `pkgs.pkgsStatic` today: - https://github.com/NixOS/nixpkgs/pull/191915 - https://github.com/NixOS/nixpkgs/issues/191920 It looks like `pkgsStatic` goes quite a bit further than what we need to build a static...
Yes that seems right. The difference that I see between the two versions is that the elm-mdl one has ripples that overlap the adjacent checkboxes, while with the plain mdl...
(Chances are it's obvious they're plain `::1`, and the only way to be confused is in the context of working with `[::1]`-style URIs? The question came up while working on...
Ran into the same thing, writing an EDN parser... The `\x0D` is certainly a bit ugly and confusing. But also not a particularly big deal.