Jeremy Miller
Jeremy Miller
I'm having this problem too, we use redlock v4 to great success so I'm downgrading for now.
We see the same thing, it happened to three or four different pods this past weekend, and is happening on a weekly basis.
~~I'm actually seeing this when valid input is given. Feels like a bug in the library itself.~~ Taking this back - any error is obscured by this cryptic error when...
> This library does not implement query and input validation to not duplicate the functionality and increase execution costs. So the error messages can vary. One option would be to...
@jquense Are you still maintaining this package?
There's a workaround for this, but it's ugly: You can create a subclass: ``` class CustomLogger extends BaseLogger { constructor( settings?: ISettingsParam, logObj?: LoggerPayload, ) { super(settings, logObj, 5); }...
Nevermind, this just breaks the logger!
To follow up on this - for production apps, are we supposed to use the `@latest` which currently maps to the 3.X series of this or should we use `v4`...