-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fix: change session start log level #9221
Conversation
I agree, that using Still, we will need a changelog entry. Side note... Items on the issue description checklist should only be marked if they are accurate - thanks! |
I don't think this is a bug, but I would not be against to change to DEBUG. |
Which file I need to edit for the changelog entry @michalsn? |
Signed-off-by: Wolf Wortmann <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
In general, we don't enter the PR number in the changelog.
Co-authored-by: Michal Sniatala <[email protected]>
Alright, should I squash or do you squash to merge? |
We can squash on merge - we just have to wait for one more approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great improvement, it was always bothering me!🤓
@element-code Thank you! |
This was a very frustrating situation for me, so I'm glad it got resolved. Also, are there no new features or updates being made to CI4? Has its development been stopped |
@mbnl What do you mean? The latest release was a month ago: https://github.com/codeigniter4/CodeIgniter4/releases/tag/v4.5.5 The new features go to the |
Description
The session class clutters out-of-the-box configured logs with debug information about its driver initialization on startup, using a
INFO
classification.This is especially problematic in authenticated webapps as every request will write at least one info message.
The message itself has a debug purpose and therefore should be classified as
DEBUG
Checklist: