19 Feb
2022
19 Feb
'22
1:01 a.m.
In regards to the aforementioned issue, we believe this is due to local Redis instance going away for a short time. This is not a common occurrence, and so this should not affect users most of the time. That being said, we will be accounting for this in our code to rid users of receiving the error when this happens, as users should not have to deal with details surrounding internal services. -- Kevin Morris Software & Linux Enthusiast