You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 6, 2024. It is now read-only.
Using a { or } in a key name causes the internal json parser to segfault
A member with a binary encoded member that has a } in it, one that is then followed by another member with a } in it, will generate invalid JSON (in the loop for i in s.chars() ) that is then parsed, causing the panic as the min and/or max scores cannot be parsed.
Adding a small console log shows the string positions being miscalculated, eg
processing i = A�','min_score':37227008,'max_score':37227263},{'member':'us}....
attached is an RDB dump that will segfault on load