| 31 Jan 2025 |
 commiterate | there's usually a gap (usually a few hours at worst) between new APIs + exceptions showing up in service and in docs. There's a separate system that gate keeps docs + SDK releases.
The server stubs (e.g. classes, exceptions), SDKs, and API docs are all generated from the same service models (e.g. Smithy or its internal predecessor). | 00:31:55 |
| commiterate | * there's usually a gap (usually a few hours at worst) between new APIs + exceptions showing up in service and in docs. There's a separate system that gate keeps docs + SDK releases.
The server stubs (e.g. classes, exceptions), SDKs, and API docs are all generated from the same service models (e.g. Smithy or its internal predecessor). The server frameworks also handle error translation so some error that's not part of the service model should never be exposed externally (gets translated into an internal server error). | 00:33:18 |
| 15 Feb 2025 |
|  BenjB83 joined the room. | 10:16:56 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:18 |
| 17 Feb 2025 |
|  p14 joined the room. | 21:48:19 |
| 19 Feb 2025 |
|  pcarrier joined the room. | 01:18:17 |
| pcarrier | Redacted or Malformed Event | 01:18:49 |
| pcarrier | * I cannot find eg ami-0017e3a9c0a557c61 or ami-07e2c5c4b1566ea6f in eu-west-3; do I need to do something to get access to the AMIs @ https://nixos.github.io/amis/ ? | 01:19:23 |
| pcarrier | Redacted or Malformed Event | 01:19:43 |
| pcarrier | * receiving:
│ Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 013b25d4-6060-4be4-bbb2-581cec95cc49, api error InvalidAMIID.NotFound: The image id '[ami-07e2c5c4b1566ea6f]' does not exist | 01:27:52 |
 Arian | You might be trying to boot up an old AMI. We only keep them for 90 days | 07:30:20 |
|  @hexa:lossy.network joined the room. | 22:32:18 |
|  adamcstephens joined the room. | 22:32:34 |
| @hexa:lossy.network | adamcstephens: first | 22:32:39 |
| adamcstephens | heh | 22:33:08 |
| adamcstephens | now that i fixed my homeserver's dns... | 22:33:19 |
| Arian | waddup | 22:33:35 |
| adamcstephens | do y'all see timeouts waiting for import snapshot with your upload jobs? | 22:33:47 |
| @hexa:lossy.network | adam asked if the room was broken 😄 so I joined | 22:33:50 |
| Arian | I don't see the messages on my laptop. Only on my phone. So maybe? | 22:34:24 |
| Arian | waddup | 22:34:31 |
| Arian | Oh my laptop is just laggy. | 22:34:40 |
| Arian | In reply to @adam:robins.wtf
do y'all see timeouts waiting for import snapshot with your upload jobs? It can happen very occasional. However the whole script is idempotent. Just rerun it and it should pick up where it left off | 22:35:08 |
| Arian | Sometimes Amazon has a bad day | 22:35:15 |
| Arian | I'm planning to move to coldsnap for snapshot uploads at some point. Which should make things more snappy | 22:35:29 |
| adamcstephens | i just noticed multiple failures today waiting on snapshot import. good to know it's fully idempotent | 22:37:10 |
| adamcstephens | maybe i'll wrap upload-ami in a loop to try a few times :) | 22:37:36 |
| adamcstephens | that or I open another PR to allow for extending the timeout | 22:38:34 |
| adamcstephens | how does the coldsnap path help? | 22:39:34 |
| Arian | coldsnap bypasses the vmimport service | 22:39:43 |
