Commit Graph

11 Commits

Author SHA1 Message Date
iliana etaoin 85823d3ade cargo update 2024-04-20 09:17:37 -07:00
iliana etaoin f9f89fdce9 cargo update (rocket v0.5!!) 2023-11-17 12:47:50 -08:00
iliana etaoin fdaf025192 cargo update 2023-09-24 10:49:58 -07:00
iliana etaoin 5986f2b1a5 cargo update 2023-07-06 23:45:16 -07:00
iliana etaoin db35bd0048 cargo update 2023-05-21 13:56:58 -07:00
iliana etaoin e0152d4bb5 cargo update 2023-04-29 10:34:47 -07:00
iliana etaoin 92c717d9fd cargo update 2023-04-06 20:32:53 -07:00
iliana etaoin 2506aa1be3 refactor error handling to catch more things 2023-04-06 20:31:41 -07:00
iliana etaoin 0a3de049b4 remove lambda support; update deps 2023-04-05 20:58:21 -07:00
iliana etaoin a926ebb0d2 cargo update; clippy lint fixes 2022-12-27 15:38:54 -08:00
iliana etaoin 67b8bd9432 Rewrite it in Rust
For the curious: this wasn't completely for no reason, although it
appears that way from the outside. I deploy this code to AWS via the
CDK, and the Python Lambda function bundler in the CDK has two unwanted
properties:

1. The assets produced by the bundler are not reproducible, due to the
   timestamps stored in the .pyc files. The bundler does nothing to
   assist with this.
2. A bug (that was reported, and that the CDK maintainers converted from
   an issue into discussion without any investigation) prevents the use
   of arm64 runtimes with this bundler. This requires emulating x86_64
   on my development machines, which are now only ARM.

... whereas the Rust function bundler I wrote does not have these
problems. So.
2022-06-24 21:16:22 -07:00