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

Better handle when log_type isn't file and give explanation #866

Merged

Conversation

joshtrichards
Copy link
Member

Fixes #52 (and possibly others)

Currently if log_type is set to anything other than file (the default) - such as syslog or systemd - the Logging page spins indefinitely. This fixes the backend assumptions about logging always being log_type file and also provides the admin (user) with an informative message so they know what's going on.

Possible follow-up work: tidy up frontend, documentation additions

@szaimen szaimen added this to the Nextcloud 27 milestone May 5, 2023
@szaimen szaimen requested review from icewind1991 and Antreesy May 5, 2023 05:52
@icewind1991 icewind1991 force-pushed the jr-better-handle-non-file-log-types branch from 0932289 to 09ef630 Compare May 10, 2023 17:37
joshtrichards and others added 2 commits May 11, 2023 13:17
Fixes nextcloud#52 (and possibly others)

Currently if `log_type` is set to anything other than `file` (the default) - such as syslog or systemd - the Logging page spins indefinitely. This fixes the backend assumptions about logging always being log_type `file` and also provides the admin (user) with an informative message so they know what's going on.

Signed-off-by: Josh Richards <[email protected]>
Signed-off-by: Robin Appelman <[email protected]>
@icewind1991 icewind1991 force-pushed the jr-better-handle-non-file-log-types branch from 09ef630 to 09efbc0 Compare May 11, 2023 11:17
Signed-off-by: Robin Appelman <[email protected]>
Copy link
Member

@icewind1991 icewind1991 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice sollution

@jdaviescoates
Copy link

Currently if log_type is set to anything other than file (the default) - such as syslog or systemd - the Logging page spins indefinitely. This fixes the backend assumptions about logging always being log_type file and also provides the admin (user) with an informative message so they know what's going on.

I actually still see the logging page spinning indefinitely so I think there may have been a regression at some point.

I'm on Nextcloud 27.1.3

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

Successfully merging this pull request may close these issues.

Logging does not load
4 participants