Closed AleksaMCode closed 8 months ago
Also, due to this bug there is another problem.
When the server is started, it doesn't create a connection to the Redis
server by default. The connection to Redis
is created when a subscriber connects, but not when a publisher connects. This means, that if the web application is started after running ASGI server without running Redis
server, it will display a toast
notification that it has connected to the server, after which the ASGI server will fail to handle Exception
s.
Redis
was never created and the Exception
is never handled correctly.Redis
server needs to be created when the ASGI server is first started.Exceptions
due to Redis
errors need to be handled.Redis
server running.Redis
serverHere is a screenshot of the error.
Is there an existing issue for this?
Description
When the server is started, it doesn't create a connection to the
Redis
server by default. The connection toRedis
is created when a subscriber connects, but not when a publisher connects.System information
2023.3
Actual Behavior
Redis
channel it fails due to the fact that the connection toRedis
was never created.Expected Behavior
Connection to
Redis
server needs to be created when the ASGI server is first started.Steps To Reproduce
Redis
serverAnything else?
Here is a screenshot of the error.![Screenshot_2023-12-18_03-52-13](https://github.com/AleksaMCode/Preferred-Network-List-Sniffer/assets/23129943/9a557ead-ae59-446c-9826-824c5a56105c)
The connection object is
None
due to the fact theRedis
connection was never created.