Skip to content
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

Config issue on v6.0.0-rc2 #106

Closed
elcheco opened this issue Aug 25, 2021 · 5 comments · Fixed by #108
Closed

Config issue on v6.0.0-rc2 #106

elcheco opened this issue Aug 25, 2021 · 5 comments · Fixed by #108

Comments

@elcheco
Copy link

elcheco commented Aug 25, 2021

I tested today v6.0.0-rc2 and an xception was thrown:

Screenshot 2021-08-25 at 16 55 05

Which corresponds to my config in local.neon:

redis:
    host: localhost
    port: 6379
    database: 0
    journal: true
    storage: true
    session:
        database: 1
        native: false
    debugger: true

The previous version didn't throw an exception on this, are there any config changes, or is it the bug?

@PavelJurasek
Copy link
Contributor

Hello @elcheco, could you please try referenced PR?

@elcheco
Copy link
Author

elcheco commented Aug 27, 2021

Hi @PavelJurasek, the exception is gone and it looks like it works, but two things:

  • I don't see the Redis Panel in Debug Bar
  • If I select all keys in the database 1, where should be the sessions - no key is shown - is in database 0 - so the database subparameter doesn't work - if I do it on 5.2 - there's the session key and content inside database 1...

@PavelJurasek
Copy link
Contributor

@elcheco please try again with the same branch

@elcheco
Copy link
Author

elcheco commented Sep 2, 2021

@PavelJurasek Sorry for the delay. Now everything looks correct and working. Sessions are in DB1, other stuff is stored in default DB0, and Redis is in the debug bar.

Thank you ;-)

@Spamercz
Copy link
Member

Spamercz commented Sep 8, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants