search

thedevdojo / voyager

Voyager - The Missing Laravel Admin
https://voyager.devdojo.com
MIT License
11.78k stars 2.67k forks source link

Error No Database connection yet in VoyagerServiceProvider loadAuth() #5339

Closed cotiga closed 3 years ago

cotiga commented 3 years ago

Version information

Description

I end up with a recurring errors that doesn't seem to be a problem for my app (but populated my log file). This error occurs even outside Voyager admin panel.

[datetime] local.ERROR: No Database connection yet in VoyagerServiceProvider loadAuth()

emptynick commented 3 years ago

Please search before opening issues. Duplicate of https://github.com/the-control-group/voyager/issues/5285, https://github.com/the-control-group/voyager/issues/5069 and https://github.com/the-control-group/voyager/issues/4045

cotiga commented 3 years ago

I had watched carefully before opening my issue, and messages like: "This is just a warning, not an error" does not suit me, thank you! Voyager seems to be at a standstill and is proving to be more and more buggy, I will take my time to create my own administration panel. Thank's for your work, but Pity :(

emptynick commented 3 years ago

But it's true, when we'd delete that line no one would notice (I actually thought about removing it). It's just saying that there is no database connection yet and will try again later.

Saying that Voyager is dead is not correct at all. We are still merging PRs. Beside that we are working hard on V2 which is why merging/releasing/triaging is just a bit slower at the moment.

emptynick commented 3 years ago

Quoted from https://github.com/the-control-group/voyager/issues/5285

The error messages was "softened" and is now an information. This message (No database connection yet in VoyagerServiceProvider loadAuth()) can be ignored safely and is definitely not the cause of any problems mentioned here.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group.