-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Precondition failed in Redis 4.1.0 when using repository pattern #180
Comments
Same here. I reverted back to 4.0.0 |
Yes, for now our recommendation is to pin Redis as |
@leonidas-o or @pankajsoni19 could I ask you to try this using: |
I have moved out of the organization where I wrote the swift based server code. So objective was to attain stability in last deployment under me. I would not be able to give time to test this out. |
@siemensikkema I guess you mean |
@leonidas-o haha, yeah how did I make that mistake? I blindly copy/pasted and adapted from another line... |
🙂 never mind and thanks for the fix. I guess this will be just the next tag after 4.1.0? |
@leonidas-o yeah this has been released in 4.1.1 |
I've got a crash on boot when redis version > 4.0.0:
But pinning to 4.0.0 helps: |
@HashedViking which version of Redis exactly is causing the crash? |
@0xTim 4.2.0
On boot I try to fetch the data previously cached in Redis, with 4.0.0 this way was ok. |
@HashedViking if you call |
yeah, calling |
Not intentionally but yes it's required because of the way Redis sets up its internal state |
Describe the bug
After updating to 4.1.0 the following error is thrown as soon as I use my cacheRepo.
The execution gets stuck at:
Routes without cacheRepo usage, are not affected. Downgrading to redis 4.0.0 shows no errors and everything works as expected.
Inside
configure.swift
redis is setup using:RedisRepo contains just the requirements from the cacheRepo protocol:
CacheRepoFactory contains:
To Reproduce
First I encountered the error after
request.cacheRepo.get(...)
was used. But it actually happens on all repo methods. As soon as you try toreturn request.eventLoop...
Steps to reproduce the behavior:
req.eventLoop.
) will throw an errorExpected behavior
No error, same behaviour like in redis 4.0.0.
Environment
The text was updated successfully, but these errors were encountered: