kindler chase

A production `.net6` service was running w/o issue for a couple of years and then started to throw the `connection was aborted by the server` exception. In this case, the...

In Nuget, this package is way too similar to the official AWS package. For inexperienced devs or those just not paying attention, this package will get installed instead of the...

Good question @hjgraca - this is not an AOT Lambda. edit: In reading through the release notes, I was wondering if AOT may have been the underlying issue for the...

@hjgraca We discovered this issue when upgrading our lambdas to .net8. We have some startup unit tests that perform some logging w/ some complex objects (classes w/ nested child classes);...

p.s. the issue UI has a dropdown for "AWS Lambda function runtime"; the only option is `.net6`. Can your team add `.net8` as an option?

@hjgraca Here's what I'm seeing. The built-in .net enum works as expected. The custom enum still logs an empty object. **Custom** * empty json object ```json { "timestamp": "", "level":...

Currently, I'm testing locally and still seeing the empty object when decorating the `Pet` enum w/ the `JsonConverter`. I'd need to deploy out to AWS and re-test. We're currently prepping...

@hjgraca I deployed a .net8 Lambda w/ v1.6.1 logger to AWS. The results are the same as my local testing: * System.Color - full serialization * Custom Enum - empty...

The only differences I'm seeing between your sample project and mine are: 1. we are using top level statement Lambdas 2. we explicitly define the output type: ```Exe``` The rest...

@hjgraca - email sent. Thanks!