endgame
endgame
The other thing we could do is log the retrying failures at a noisier log level, but we've gotten this far without it so let's get 2.0 out first and...
Seems easy and important. I'll add it to the milestone. May need to add an extra type to the generator config, to enable plugin-based modification of how we react to...
That would be nice, but we've survived for years without it, so it's not critical for getting 2.0 out the door. That said, I'd look at a PR.
Yes, that's right. There shouldn't be any in the generated service bindings, so you'll only be looking for ones in `lib/amazonka` and `lib/amazonka-core`. You should hopefully also be able to...
Stack support is another consideration: https://github.com/commercialhaskell/stack/issues/52561
Yeah. That's pretty recent so can probably be taken as true. If we move to multiple public libraries in a single package (if/when Hackage supports that), we may create more...
That's good news. Still need to check where hackage is at with all this stuff, as well as cabal2nix and haskell.nix. No point getting a whizz-bang new version of Amazonka...
Your plan to add a `useAcceleratedEndpoint` sounds reasonable, but I haven't thought deeply and don't know how you'll do that. You'll probably need to fiddle the files in `config/` in...
Status update: We won't hit the the planned release date, and with Christmas nearly upon us that's going to slow everything down more. Mid-January seems more realistic. There are things...