Closed nicks closed 2 months ago
probably the simplest fix is to move the isStrictSemvar
check here --
inside the try...catch block
Hi @nicks, thank you for reporting this issue and for suggesting a solution. We have created a PR (https://github.com/Unleash/unleash-client-node/pull/648) that implements your suggested fix. Once the PR is merged, we plan to release a new version of the proxy that will include this fix.
By any chance, could you please share what your context looks like for this field? This information would help us ensure that we have covered this edge case in our tests.
Thank you again for your contribution. Your suggestion was spot on and should help prevent similar issues in the future.
Edit: This fix is now available in Unleash Proxy v1.4.4.
@nunogois wow, thank you for the quick fix!
How would I go about getting the context for this field? I mainly pulled this trace from server logs, I don't have much more context than that.
Describe the bug
Unleash proxy crashed over the weekend, seen in our logs:
Steps to reproduce the bug
Not sure yet how to repro, still digging, was hoping you might have a guess? might be bad data on the settings side
Expected behavior
proxy not to crash
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
unleashorg/unleash-proxy:v1.2.0
Subscription type
None
Hosting type
None
SDK information (language and version)
No response