-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Auto-configure repositories for Redis #5448
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
Comments
There is a RedisTestServer that runs if redis is available. I would use that. Are you going to submit a PR for this? |
Thanks @snicoll PR is under way. |
Closing in favour of the PR #5455 |
* pr/5455: Polish contribution Auto-configure Redis repositories
Seems to break the latest Buildpack.
|
@philwebb I altered |
@nebhale Did you have a way to replicate this issue? |
@philwebb Our system tests would reproduce it. Can I update to the latest |
@nebhale We've not made any changes to fix it as yet. I just wanted a way to reproduce locally if possible. |
@nebhale how can I test this? Does it work with |
@nebhale can you help? It's a blocker for M2 and we're about to release it. I am still not sure what the problem is. |
@snicoll This works with M1 in our system tests, but if I release that to the snapshot it starts failing again. I can check a snapshot if an update has been made. |
You said that already. I don't know what those system tests are and nothing indicates that this failure is related to this commit. It's failing quite low so that's why I am asking for a way to reproduce myself... |
Problem seems to be because FakeRedisConnectionFactory returns |
Hopper RC1 brings support for Redis repositories. We should improve our auto-configuration to support that as well.
See gh-5150
The text was updated successfully, but these errors were encountered: