tjhiggins

I was just about to create a similar issue. Agreed with @liorfranko on picking the cheapest, but falling back to the next available. Also using spot and running out of...

> Class C CIDRs are too small for EKS given each pod eats one IP. Take a look https://aws.amazon.com/blogs/containers/addressing-ipv4-address-exhaustion-in-amazon-eks-clusters-using-private-nat-gateways/ Can you still expose services publicly if you use a private...

> @tjhiggins "carrier grade NAT" is an industry name. It has nothing to do with AWS VPC Nat Gateways. Nothing changes in that part of the infrastructure. > > Karpenter...

@manast I'm also curious about this. When redis is down my nestjs api will "start", but all requests will hang. Isolated it down to the registerQueue, but unclear why its...

> I am leaning towards an option where you can choose if you want to wait for the connection to be ready or not, as otherwise there will always be...

@maxi297 any updates here? This seems to be a blocker for me using airbyte for Chorus's api. I can incrementally pull conversations, but they don't include the transcript. So I...

> @tjhiggins This has been deemed not aligned with our team's current goals. We will re-evaluate before the next cycle which is around mid-November Thanks for the update.

> FWIW, This can be achieved in the same way with the current interceptor setup. e.g. > > ```js > return (dispatch: Dispatcher['dispatch']) => { > return function intercept(requestOptions: Dispatcher.DispatchOptions,...

This feels pretty bad, but it seems to work: ```ts export function createLoggingInterceptor({ projectId, name }: LoggingOptions) { const logging = new Logging({ projectId, autoRetry: true, maxRetries: 3 }); const...

> Yeah, AsyncGenerators cannot be re-used/consumed in parallel. > > Can you elaborate why bad? The interceptors API has been made for these kind of purposes The onBodySent callback is...