Anton Pirker

Yes, a solution in the UI is the only way. The SDK does now know about config changes and I also think we should not implement something like this.

Hey @vakorol Thanks for reporting this and the good description of the problem. We will look into this.

With duplication of code this will make maintaining the prose text in the documentation harder, and the same page in different versions *will* diverge. This is something we need to...

Another thing (maybe not fully related to this RFC). I would love to render the "[options](https://docs.sentry.io/platforms/javascript/configuration/options/)" sections from source code. We could add this documentation to the source and then...

> > Another thing (maybe not fully related to this RFC). > > I would love to render the "[options](https://docs.sentry.io/platforms/javascript/configuration/options/)" sections from source code. We could add this documentation to...

Hey @cmanallen ! This is the best PR I have received ever! Great work. The integrations should not change the Scope. I have created an commit on your branch to...

Hey @omerfarukabaci I just read the whole thread and I would like to help. > I was wondering that, to make sure it is (or it isn't) related with Sentry...

Hey @Fwang36 Thanks for reporting this! One thing to consider: If people add the AWS Layer to their function (instrumenting their Lambda function without changing their code) they can not...

Maybe we should add an env var to the layer instrumentation to enable/disable the debug flag in sentry.init().

As the users can set the [`timeout_warnings` option](https://docs.sentry.io/platforms/python/integrations/aws-lambda/manual-instrumentation/#options) I will close this issue.