Stijn De Haes

In nginx for example you can set a response size before compression is even considered. Probably that would make sense for this as well?

I see you are assigned @krol3, don't know if you are working on it or this is still relevant. But if it's still relevant and you are ok with this...

@DirectXMan12 Since it's been a long time ago I think it's better that I propose what I think I have to do before starting so here it goes: - The...

We are seeing memory leaks in production for one of our applications. Could these dummy segments be the culprit? I see most memory usage is in Xray for the moment,...

Hi @willarmiros, thank you very much! I yesterday just upgraded to the commit with the fix on main and saw immediate results, memory pressure was way down, so I can...

@byrnedo As a temporary workaround in your go.mod file you can point to [this commit](https://github.com/aws/aws-xray-sdk-go/commit/a735b941af42038e992486e70fae5419589b658c) by replacing: ``` require ( .... github.com/aws/aws-xray-sdk-go v1.7.0 ... ) ``` with: ``` require (...

Release [1.7.1](https://github.com/aws/aws-xray-sdk-go/blob/master/CHANGELOG.md#release-v171-2022-09-14) includes the fix for the memory leak. I believe this issue can be closed

Still no progress?

@adrianludwin that would be fine for me. So we add the option to the `CertRotator` struct and in the `AddRotator` call we do something like: ``` func AddRotator(mgr manager.Manager, cr...

I would be all for doing semver and making this a breaking change in a major release or something similar :)