cannot use middleware.Logger() (value with invalid type) as echo.MiddlewareFunc value in argument to e.UseLSP
jwt.io valid token to JWT eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE0NjE5NTcxMzZ9.RB3arc4-OyzASAaUhC2W3ReWaXAt_z2Fd3BN4aWTgEY jwt.io secret base64 encoded token (Send to my framework) eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE0NjE5NTcxMzZ9.3Lgl_HITxQsQbEu-23QVeDrcktpYIHBAhECGWqGZOhk
I am using echo version v4.1.0.
Observing that in an http request, information which is set in echo context using echo.Context.Set() and retrieved back using echo.Context.Get() in the same http request, across middlewares, is found to have leaking information from different requests.
The .Get() method is giving back data which was .Set() in some other http request.
Looked around for similar issue and found this link labstack/echo#273 which says the echo context was made concurrent safe in labstack/echo#1158
But the issue still coming.
I do not have a publicly shareable code yet but it is doing the following:
This is seen only under high load and reproduction is not trivial.
Any pointers ?