Redis client not found when created background tasks in Swagger

[scottyeung]

Describe the bug or question
A clear and concise description of what the bug or question is.

To Reproduce
Please provide a self-contained, minimal, and reproducible example of your use case

async def is_rate_limited(db: AsyncSession, user_id: int, path: str, limit: int, period: int) -> bool:
    if client is None:
        logger.error("Redis client is not initialized.")
        raise Exception("Redis client is not initialized.")

Description
Redis client was recognised as none when I tried to create background tasks in Swagger and caught exception in is_rate_limited

Screenshots

Additional context
Add any other context about the problem here.

[igorbenav]

How did you run it? Using docker compose?

[scottyeung]

How did you run it? Using docker compose?

Exactly, docker-compose. Did I miss anything?

[studentNinja]

Having the exact same issue.
Redis name in .env = redis ,
App started by docker compose up -d
When trying to post a new task , getting raise Exception("Redis client is not initialized.")=

[yucelz]

I think the issue is that all the Redis connections and the pool are tied to the cache in setup.py, which means that anyone who isn't using the cache can't get to them.

I came up with a temporary fix. It's not ideal, but it does the job. I moved everything, like the is_rate_limited function, into cache.py, and now it works just fine.

[mlm-master]

With our without cache, i'm still having the same exact issue too. Upon debugging, I can see that the Redis rate_limit.client instantiated when the application is starting.

However, the Redis client object somehow gets destroy and become None when the API endpoint is called:

The issue only occurs on redis rate limiter object, but not on redis cache object