Ugo Riboni

From what I can see the collector `main` is simply [calling `NextEvent` in a loop](https://github.com/open-telemetry/opentelemetry-lambda/blob/ca152eb7993e0d2e37e1b85d08d1612d91e02d0d/collector/main.go#L69). `NextEvent()` simply calls the `Next` API on the extension API. According to the [lambda extension...

I am also getting this same issue, using version 1.6.0 of the ADOT layer (JS). I noticed that there are two patterns of usage, one of which makes the issue...

This still happens with version 1.7.0 of the layer. I posted [here](https://github.com/open-telemetry/opentelemetry-lambda/issues/224#issuecomment-1273450935) a quick analysis of what seems to cause the problem in the interaction between the collector and the...

Hello, I hate to be "that guy" but... [the list](https://opentelemetry.io/vendors/) still has no explanation to what "Native OTLP" means. In my mind, it means they run an OTLP receiver, and...

Wouldn't it be possible to prevent this vulnerability by simply changing the "wrapper" to include a return statement ? Right now what the wrapper does is essentially `with (sandbox) {...

Also wouldn't it be also possible to escape the sandbox by simply getting hold of any function, reaching its constructor (i.e. Function), then using it to create a new un-sandboxed...

For what is worth, I have tested this branch and it seem to do what it says. Hopefully it will be merged soon, as it's really useful not to be...

I am testing the branch and things seem to work better, but I have some strange results still. Basically the exporter seems to successfully send the traces to honeycomb.io in...

> I don't think it is the responsibility of the community to help end-users making a choice which vendor to use. Fair enough. But in that case, why not just...

I am testing version 1.0.5-0 which, as I understand it, is a pre-release for the fix to this issue. It works OK if I put `"moduleResolution":"node16"` in my `tsconfig.json`. However...