Heitor Lessa
Heitor Lessa
Meeting tomorrow one last time, Joshua. So far, we’ve discovered that all languages behave like that, and it’s a case of “it’s a feature not a bug” in the way...
Good news! Met with Lambda engineering to rule out options, and we have a potential solution for all runtimes. I say potential because security review might take a while to...
Sadly no Kristoffer, the solution Lambda team thought it was possible didn’t end up being robust enough - they’re revisiting it after 3.12 is launched, as it affects all languages...
That unfortunately causes another unwanted side effect @tlinhart -- any `warnings` coming from libraries or your own emitted warnings will be dropped with this configuration. The new ALC (Advanced Lambda...
I haven't tried but I suspect if you explicitly use `captureWarnings(True)` it might work because ALC feature changes the Root Logger. If my memory serves, `captureWarnings(True)` configures a logger named...
TL;DR - we're still working with the AWS Lambda team on this, and related issues with the newly launched Advanced Logging Control like the warning above.
Hey Julian!! Not yet, we’re still waiting to hear from Lambda whether this will be fixed on runtime for all languages. We don’t plan to remove the flag until we...
**HELP WANTED** -- here's a backup plan that wouldn't involve a no-op Lambda internal extension. We know nearly all customers use the decorator `@logger.inject_lambda_context` to enrich the Lambda context, opportunistically...
hey @nico00, please allow me to ask some clarifying questions > BatchProcessingError is raised when all records failed to be processed. In such case, processor response appears empty, as all...