Maxime David

I'm closing this as I think all runtimes have now been udpated to al2023. Let me know otherwise and I can re-open

Hey! Thanks for your contribution! Yeah, currently the load() is called once and filtering is done client side when you change filters. We might want to keep that. Having more...

I don't think there are region-specific runtimes so maybe : ``` { "memorySizes": [128, 256, 512, 1024], "regions":["us-east-1", "eu-west-1", xxx] "runtimes": [ { ``` would make more sense?

hey @pragmaticivan Are you talking about an example using this package? https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-aws-lambda or something else?

upstream PR has been approved :) and should be merged soon

upstream PR has been merged, will follow-up with bumping when it will be released

Interesting! I will test with a sleep to see if that affects the number. Thanks for reporting it @ledoux7

I could not reproduce, when you say `It possibly takes some time before AWS has made the snapstart feature enabled on newly updated functions`, are you referring to the docs...

@serkan-ozal According to the doc (ref: https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users#about-issue-and-pull-request-assignees) I would need read permission (as I am already a member of the opentelemetry org). So I think you need to add me...

@wpessers interesting! You're absolutely right, the issue is that by default devDependencies are >not< updated by dependabot [(I've just discovered that I have the same issue in my repo)](https://github.com/maxday/lambda-perf/blame/main/result-builder/package.json), you...